Systems and methods for allocating vehicle costs between vehicle users for anticipated trips

ABSTRACT

Vehicle costs may be allocated between users of a vehicle, including autonomous vehicles. A vehicle cost allocation (VCA) computing device receives an anticipated trip report associated with an anticipated future trip, the anticipated trip report associated with at least one vehicle user including an anticipated driver of the vehicle and an anticipated passenger, the anticipated trip report including at least one of an anticipated destination and a distance of the anticipated future trip. The VCA computing device is also configured to determine one or more anticipated vehicle costs for the anticipated future trip. The vehicle costs may include usage-based or trip-based insurance. The VCA computing device is also configured to allocate a respective portion of the vehicle cost to the anticipated driver and passenger and transmit the anticipated vehicle costs to for review by the anticipated driver.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority to U.S. ProvisionalPatent Application No. 62/334,803, filed May 11, 2016, entitled “SYSTEMSAND METHODS FOR ALLOCATING VEHICLE COSTS BETWEEN VEHICLE USERS” and U.S.Provisional Patent Application No. 62/345,445, filed Jun. 3, 2016,entitled “SYSTEMS AND METHODS FOR ALLOCATING VEHICLE COSTS BETWEENVEHICLE USERS”, U.S. Provisional Patent Application No. 62/418,611,filed Nov. 7, 2016, entitled “SYSTEMS AND METHODS FOR ALLOCATING VEHICLECOSTS BETWEEN VEHICLE USERS”, U.S. Provisional Patent Application No.62/436,194, filed Dec. 19, 2016, entitled “SYSTEMS AND METHODS FORALLOCATING VEHICLE COSTS BETWEEN VEHICLE USERS,” and U.S. ProvisionalPatent Application 62/438,193, filed Dec. 22, 2016, entitled “SYSTEMSAND METHODS FOR ALLOCATING VEHICLE COSTS BETWEEN VEHICLE USERS,” theentire contents and disclosure of which are hereby incorporated hereinin their entirety.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to vehicle costs and, moreparticularly to systems and methods for dividing and allocating vehiclecosts between users of a vehicle.

BACKGROUND

As car buyers become ever more finance and eco-conscious, vehiclemanufacturers have responded by offering new buying options, includingshared-ownership/shared-lease options. These options may offer carowners and lessors the opportunity to share responsibility and cost forthe vehicle between multiple vehicle users, reducing the financialburden and the environmental impact of vehicle usage. However, these newoptions also present issues for these vehicle users in how they willsplit those vehicle costs—including insurance, fuel, and maintenancecosts, among others—in the manner they find most equitable and fair.Even if these vehicle users can agree on one or more of thesecost-sharing issues, even more problems arise when considering how tomanage the actual allocation and subsequent payment of those costs.

BRIEF SUMMARY

The present embodiments may relate to systems and methods for dividingand allocating vehicle costs between multiple vehicle users of avehicle. A shared vehicle system including a vehicle cost allocation(VCA) computing device may receive and process vehicle policiesagreed-upon by all of the vehicle users. These vehicle policies maydescribe how one specific set of vehicle users chooses to divide andallocate any kind of vehicle costs. The VCA computing device may thentrack usage of the vehicle by each vehicle user and, according the usageand the vehicle policies, allocate a portion of a total operating costof the vehicle to each vehicle user. In some embodiments, the VCAcomputing device may also manage payment of those vehicle costs onbehalf of the vehicle users.

In one aspect, a vehicle cost allocation (VCA) computing device forallocating vehicle costs between users of a vehicle, such as anautonomous or semi-autonomous vehicle, may be provided. The VCAcomputing device may include a memory and a processor. The processor maybe programmed to receive a potential trip report associated with apotential future trip to be performed using a vehicle. The potentialtrip report may be associated with at least one vehicle user includingan anticipated driver of the vehicle and an anticipated passenger, andmay include an anticipated destination. The processor may also beprogrammed to retrieve insurance policy information associated with atleast one of the vehicles and the anticipated driver of the vehicle, andgenerate an anticipated insurance cost based upon the anticipated driverof the vehicle and the anticipated destination. The processor may befurther programmed to allocate the anticipated insurance cost betweenthe anticipated driver and the anticipated passenger, and transmit theanticipated insurance cost to one or more computing devices for reviewby the anticipated driver. The processor may be programmed to performadditional, fewer, or alternative actions, including those discussedelsewhere herein.

In another aspect, a computer-implemented method for allocating vehiclecost between users of a vehicle may be provided. The method may beimplemented using a vehicle cost allocation (VCA) computing deviceincluding a processor in communication with a memory. The method mayinclude receiving a potential trip report associated with a potentialfuture trip to be performed using a vehicle. The potential trip reportmay be associated with at least one vehicle user including ananticipated driver of the vehicle and an anticipated passenger, and mayinclude an anticipated destination. The method may also includeretrieving insurance policy information associated with at least one ofthe vehicle and the anticipated driver of the vehicle, and generating ananticipated insurance cost based upon the anticipated driver of thevehicle and the anticipated destination. The method may further includeallocating the anticipated insurance cost between the anticipated driverand the anticipated passenger, and transmitting the anticipatedinsurance cost to one or more computing devices for review by theanticipated driver. The method may include additional, fewer, oralternative actions, including those discussed elsewhere herein.

In a further aspect, a vehicle cost allocation (VCA) computing devicefor allocating vehicle costs between users of a vehicle may be provided.The VCA computing device may include a memory and a processor. Theprocessor may be programmed to receive a trip report associated with atrip performed using a vehicle. The trip report may be associated with aplurality of vehicle users of the vehicle and may include anidentification of a distance of the trip. The processor may also beprogrammed to determine which vehicle user of the plurality of vehicleusers is a driver of the trip, and retrieve insurance policy informationassociated with the driver of the trip. The processor may be furtherprogrammed to calculate an insurance cost associated with the trip basedat least in part upon the insurance policy information and the distanceof the trip, and allocate the insurance cost between the plurality ofvehicle users. The processor may be programmed to perform additional,fewer, or alternative actions, including those discussed elsewhereherein.

In yet another aspect, a computer-implemented method for allocatingvehicle costs between users of a vehicle may be provided. The method maybe implemented using a vehicle cost allocation (VCA) computing deviceincluding a processor and a memory. The method may include receiving atrip report associated with a trip performed using a vehicle. The tripreport may be associated with a plurality of vehicle users of thevehicle, and may include an identification of a distance of the trip.The method may also include determining which vehicle user of theplurality of vehicle users is a driver of the trip, and retrievinginsurance policy information associated with the driver of the trip. Themethod may further include calculating an insurance cost associated withthe trip based at least in part upon the insurance policy informationand the distance of the trip, and allocating the insurance cost betweenthe plurality of vehicle users. The method may include additional,fewer, or alternative actions, including those discussed elsewhereherein.

In one aspect, a vehicle cost allocation (VCA) computing device forallocating vehicle costs between users of a vehicle may be provided. TheVCA computing device may include a memory and a processor. The processormay be programmed to receive a plurality of trip reports associated witha corresponding plurality of trips performed using a vehicle within apredetermined interval of time. Each trip of the plurality of trips maybe associated with one or more vehicle users of a plurality of vehicleusers associated with the vehicle. The processor may also be programmedto generate a total vehicle usage report based at least in part upon theplurality of trip reports. The total vehicle usage report may describethe total usage of the vehicle by the plurality of vehicle users overthe interval of time. The processor may be further programmed todetermine a total vehicle cost associated with the vehicle over theinterval of time based at least in part upon the total vehicle usagereport, and generate a respective user usage report associated with eachvehicle user of the plurality of vehicle users, based at least in partupon one or more trip reports of the plurality of trip reportsassociated with the corresponding vehicle user. The processor may alsobe programmed to determine a respective vehicle user cost attributableto each vehicle user of the plurality of vehicle users based at least inpart upon the corresponding user usage report for the correspondingvehicle user and the total vehicle cost. The processor may be stillfurther programmed to allocate each respective vehicle user cost to thecorresponding vehicle user. The processor may be programmed to performadditional, fewer, or alternative actions, including those discussedelsewhere herein.

In another aspect, a computer-implemented method for allocating vehiclecosts between users of a vehicle may be provided. The method may beimplemented using a vehicle cost allocation (VCA) computing deviceincluding a processor and a memory. The method may include receiving aplurality of trip reports associated with a corresponding plurality oftrips performed using a vehicle within a predetermined interval of time.Each trip of the plurality of trips may be associated with one or morevehicle users of a plurality of vehicle users associated with thevehicle. The method may also include generating a total vehicle usagereport based at least in part upon the plurality of trip reports. Thetotal vehicle usage report may describe the total usage of the vehicleby the plurality of vehicle users over the interval of time. The methodmay further include determining a total vehicle cost associated with thevehicle over the interval of time based at least in part upon the totalvehicle usage report, and generating a respective user usage reportassociated with each vehicle user of the plurality of vehicle users,based at least in part upon one or more trip reports of the plurality oftrip reports associated with the corresponding vehicle user. The methodmay also include determining a respective vehicle user cost attributableto each vehicle user of the plurality of vehicle users based at least inpart upon the corresponding user usage report for the correspondingvehicle user and the total vehicle cost. The method may still furtherinclude allocating each respective vehicle user cost to thecorresponding vehicle user. The method may include additional, fewer, oralternative actions, including those discussed elsewhere herein.

In yet another aspect, at least one non-transitory computer-readablestorage media having computer-executable instructions embodied thereonmay be provided. When executed by one or more processors, thecomputer-executable instructions may cause the one or more processors toreceive a plurality of trip reports associated with a correspondingplurality of trips performed using a vehicle within a predeterminedinterval of time. Each trip of the plurality of trips may be associatedwith one or more vehicle users of a plurality of vehicle usersassociated with the vehicle. The computer-executable instructions mayalso cause the one or more processors to generate a total vehicle usagereport based at least in part upon the plurality of trip reports. Thetotal vehicle usage report may describe the total usage of the vehicleby the plurality of vehicle users over the interval of time. Thecomputer-executable instructions may further cause the one or moreprocessors to determine a total vehicle cost associated with the vehicleover the interval of time based at least in part upon the total vehicleusage report, and generate a respective user usage report associatedwith each vehicle user of the plurality of vehicle users, based at leastin part upon one or more trip reports of the plurality of trip reportsassociated with the corresponding vehicle user. The computer-executableinstructions may also cause the one or more processors to determine arespective vehicle user cost attributable to each vehicle user of theplurality of vehicle users based at least in part upon the correspondinguser usage report for the corresponding vehicle user and the totalvehicle cost. The computer-executable instructions may still furthercause the one or more processors to allocate each respective vehicleuser cost to the corresponding vehicle user. The computer-executableinstructions may cause the one or more processors to perform additional,fewer, or alternative actions, including those discussed elsewhereherein.

In a further aspect, a vehicle cost allocation (VCA) computing devicefor allocating vehicle costs between users of a vehicle, the vehiclecosts including an insurance cost, may be provided. The VCA computingdevice may include a memory and a processor. The processor may beprogrammed to receive a trip report associated with a trip performedusing a vehicle, the trip associated with one or more vehicle users of aplurality of vehicle users of the vehicle. The processor may also beprogrammed to determine which vehicle user of the one or more vehicleusers is a driver for the trip, and retrieve insurance policyinformation associated with the driver. The processor may be furtherprogrammed to retrieve one or more vehicle policies provided by theplurality of vehicle users, and determine an insurance cost associatedwith the trip based at least in part upon the insurance policyinformation and the one or more vehicle policies. The processor may bestill further programmed to allocate the insurance cost between the oneor more vehicle users. The processor may be programmed to performadditional, fewer, or alternative actions, including those discussedelsewhere herein.

In another aspect, a computer-implemented method for allocating vehiclecosts between users of a vehicle, the vehicle costs including aninsurance cost, may be provided. The method may be implemented using avehicle cost allocation (VCA) computing device including a processor anda memory. The method may include receiving a trip report associated witha trip performed using a vehicle, the trip associated with one or morevehicle users of a plurality of vehicle users of the vehicle. The methodmay also include determining which vehicle user of the one or morevehicle users is a driver for the trip, and retrieving insurance policyinformation associated with the driver. The method may further includeretrieving one or more vehicle policies provided by the plurality ofvehicle users, and determining an insurance cost associated with thetrip based at least in part upon the insurance policy information andthe one or more vehicle policies. The method may still further includeallocating the insurance cost between the one or more vehicle users. Themethod may include additional, fewer, or alternative actions, includingthose discussed elsewhere herein.

In one aspect, a vehicle cost allocation (VCA) computing device formanaging payment of vehicle costs for users of a shared vehicle may beprovided. The VCA computing device may include a memory and a processor.The processor may be programmed to determine a respective portion of atotal vehicle cost to be allocated to each vehicle user of a pluralityof vehicle users associated with a vehicle, the total vehicle costassociated the vehicle over a predetermined interval of time. Theprocessor may also be programmed to access a respective pre-paid accountassociated with each vehicle user, and transmit instructions to arespective financial institution associated with each pre-paid accountto withdraw funds corresponding to the respective portion of the totalvehicle cost. The processor may be programmed to perform additional,fewer, or alternative actions, including those discussed elsewhereherein.

In a still further aspect, a computer-implemented method for managingpayment of vehicle costs for users of a shared vehicle may be provided.The method may be implemented using a vehicle cost allocation (VCA)computing device including a processor and a memory. The method mayinclude determining a respective portion of a total vehicle cost to beallocated to each vehicle user of a plurality of vehicle usersassociated with a vehicle, the total vehicle cost associated the vehicleover a predetermined interval of time. The method may also includeaccessing a respective pre-paid account associated with each vehicleuser, and transmitting instructions to a respective financialinstitution associated with each pre-paid account to withdraw fundscorresponding to the respective portion of the total vehicle cost. Themethod may include additional, fewer, or alternative actions, includingthose discussed elsewhere herein.

In one aspect of the present disclosure, a vehicle cost allocation (VCA)computing device for allocating vehicle costs between users of a vehiclemay be provided. The VCA computing device may include a memory and aprocessor, wherein the processor is programmed to receive vehicletelematics data from one or more sensors within the vehicle, and, basedupon the received vehicle telematics data, identify one or more vehicleusers present in the vehicle during a trip. The processor may be furtherprogrammed to determine a vehicle cost associated with the trip, andallocate a respective portion of the vehicle cost to each of the one ormore vehicle users. The processor may be programmed to performadditional, fewer, or alternative actions, including those discussedelsewhere herein.

In another aspect, a computer-implemented method for allocating vehiclecosts between users of a vehicle may be provided. The method may beimplemented using a vehicle cost allocation (VCA) computing deviceincluding a processor and a memory. The method may include receivingvehicle telematics data from one or more sensors within the vehicle, andbased upon the received vehicle telematics data, identifying one or morevehicle users present in the vehicle during a trip. The method may alsoinclude determining a vehicle cost associated with the trip, andallocating a respective portion of the vehicle cost to each of the oneor more vehicle users. The method may include additional, fewer, oralternative actions, including those discussed elsewhere herein.

In a further aspect, at least one non-transitory computer-readablestorage media having computer-executable instructions embodied thereonmay be provided. When executed by one or more processors, thecomputer-executable instructions may cause the one or more processors toreceive vehicle telematics data from one or more sensors within thevehicle, and based upon the received vehicle telematics data, identifyone or more vehicle users present in the vehicle during a trip. Thecomputer-executable instructions may also cause the one or moreprocessors to determine a vehicle cost associated with the trip, andallocate a respective portion of the vehicle cost to each of the one ormore vehicle users. The computer-executable instructions may cause theone or more processors to perform additional, fewer, or alternativeactions, including those discussed elsewhere herein.

In another aspect, a vehicle cost allocation (VCA) computing device forallocating vehicle costs between users of an autonomous vehicle may beprovided. The VCA computing device may include a memory and a processor,wherein the processor is programmed to receive vehicle telematics datafrom one or more sensors within the autonomous vehicle, and, based uponthe received vehicle telematics data, identify one or more vehicle userspresent in the autonomous vehicle during one or more trips performedusing the autonomous vehicle. The processor may also be programmed todetermine a vehicle cost associated with the one or more trips, andallocate a respective portion of the vehicle cost to each of the one ormore vehicle users based upon their respective presence in theautonomous vehicle during the one or more trips. The processor may beprogrammed to perform additional, fewer, or alternative actions,including those discussed elsewhere herein.

In a still further aspect, a computer-implemented method for allocatingvehicle costs between users of an autonomous vehicle may be provided.The method may be implemented using a vehicle cost allocation (VCA)computing device including a processor and a memory. The method mayinclude receiving vehicle telematics data from one or more sensorswithin the autonomous vehicle, and, based upon the received vehicletelematics data, identifying one or more vehicle users present in theautonomous vehicle during one or more trips performed using theautonomous vehicle. The method may also include determining a vehiclecost associated with the one or more trips, and allocating a respectiveportion of the vehicle cost to each of the one or more vehicle usersbased upon their respective presence in the autonomous vehicle duringthe one or more trips. The method may include additional, fewer, oralternative actions, including those discussed elsewhere herein.

Advantages will become more apparent to those skilled in the art fromthe following description of the preferred embodiments which have beenshown and described by way of illustration. As will be realized, thepresent embodiments may be capable of other and different embodiments,and their details are capable of modification in various respects. Inaddition, although certain steps of the exemplary processes arenumbered, having such numbering does not indicate or imply that thesteps necessarily have to be performed in the order listed. The stepsmay be performed in the order indicated or in another order.Accordingly, the drawings and description are to be regarded asillustrative in nature and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

The Figures described below depict various aspects of the systems andmethods disclosed therein. It should be understood that each Figuredepicts an embodiment of a particular aspect of the disclosed systemsand methods, and that each of the Figures is intended to accord with apossible embodiment thereof. Further, wherever possible, the followingdescription refers to the reference numerals included in the followingFigures, in which features depicted in multiple Figures are designatedwith consistent reference numerals.

There are shown in the drawings arrangements which are presentlydiscussed, it being understood, however, that the present embodimentsare not limited to the precise arrangements and are instrumentalitiesshown, wherein:

FIG. 1 illustrates a schematic diagram of an exemplary shared vehiclesystem;

FIG. 2 illustrates a schematic diagram of an exemplary vehicle costallocation (VCA) computing device that may be used in the shared vehiclesystem shown in FIG. 1;

FIG. 3 illustrates a schematic diagram of an exemplary vehicle that maybe used in the shared vehicle system shown in FIG. 1;

FIG. 4 illustrates a data flow diagram showing exemplary paymentmanagement functionality of the VCA computing device shown in FIG. 2;

FIG. 5 illustrates an exemplary configuration of an exemplary usercomputing device shown in FIG. 1, in accordance with one embodiment ofthe present disclosure;

FIG. 6 illustrates an exemplary configuration of an exemplary servercomputer device shown in FIG. 1, in accordance with one embodiment ofthe present disclosure;

FIG. 7 illustrates a flow chart of an exemplary computer-implementedmethod for allocating vehicle costs between users of a vehicle, usingthe shared vehicle system shown in FIG. 1;

FIG. 8 illustrates a diagram of components of one or more exemplarycomputing devices that may be used in the shared vehicle system shown inFIG. 1;

FIG. 9 illustrates a flow chart of another exemplarycomputer-implemented method for allocating vehicle costs between usersof a vehicle, using the shared vehicle system shown in FIG. 1;

FIG. 10 illustrates a flow chart of yet another exemplarycomputer-implemented method for allocating vehicle costs between usersof a vehicle, using the shared vehicle system shown in FIG. 1; and

FIG. 11 illustrates a schematic diagram of an exemplary autonomous orsemi-autonomous vehicle that may be used in the shared vehicle systemshown in FIG. 1.

The Figures depict preferred embodiments for purposes of illustrationonly. One skilled in the art will readily recognize from the followingdiscussion that alternative embodiments of the systems and methodsillustrated herein may be employed without departing from the principlesof the invention described herein.

DETAILED DESCRIPTION

The present embodiments may relate to, inter alia, systems and methodsfor dividing and allocating vehicle costs between users of a vehicle.More and more car-sharing programs are being created, in an effort toreduce transportation costs as well reduce environmental impact. Somecar companies are going so far as to offer multiple-lessee car leases,or “co-leases.” These projects may create situations in whichcost-sharing plans and rules may be necessary, to avoid disputes andother similar problems among “co-owners” or other users of the vehicle.

The systems and methods described herein are directed to implementing acost-sharing structure based upon a plurality of rules or policiesagreed upon by all users of the vehicle. These “vehicle policies” maydefine who is responsible for particular portions of vehicle-relatedcosts, such as insurance, fuel, maintenance, incidental, and/or othervehicle costs. For example, some costs may be split evenly between allvehicle users all of the time (e.g., a maintenance cost associated withan oil change). Other costs may be divided and allocated based uponindividual and/or multi-user use (e.g., fuel costs divided based uponwhich user(s) is present on and/or responsible for each trip). Somecosts may be divided and allocated based upon certain risk factors(e.g., insurance costs split based upon who is driving). Still othercosts may be fully allocated to a single user (e.g., incidental costssuch as toll costs may be only allocating to the commuting user usingtoll roads, or incidental costs such as a repair cost for an accident).

These vehicle policies may be automatically generated (e.g., by thesystem) and/or may be manually edited, updated, and/or requested by oneor more vehicle users in a “setup” or “registration” phase. Thisregistration phase may occur when one or more of the vehicle usersretrieves the vehicle, for example, at a car dealership. In anotherembodiment, this registration phase may occur when the vehicle userschoose to register with a vehicle cost allocation service. It should beunderstood that changes to an agreed-upon vehicle policy may be madewith the approval of all vehicle users associated with the vehicle/thevehicle policy. In some embodiments, for some vehicle policies, suchchanges may further require approval of at least one other party, suchas an insurance underwriter or a lessor.

In the exemplary embodiments, the vehicle cost allocation services maybe provided and performed by a vehicle cost allocation (VCA) computingdevice. The VCA computing device may process the vehicle policies todetermine how the vehicle users have agreed to divide and allocate costsassociated with the vehicle. The VCA computing device may communicatewith the vehicle and the vehicle users (e.g., using one or morecomputing devices associated with respective vehicle users) to trackvehicle usage and vehicle costs. The VCA computing device may thendivide vehicle costs in accordance with the agreed-upon vehiclepolicies, and allocate respective portions of the vehicle costs to thevehicle users. In some embodiments, the vehicle users may manage paymentof the vehicle costs. In other embodiments, the VCA computing device maymanage payments, for example, by transmitting withdrawal and transferinstructions to respective financial account(s) associated with thevehicle users.

“Vehicle,” as used herein, may refer generally to any vehicle owned,operated, and/or used by one or more vehicle users. A vehicle mayinclude any kind of vehicle, such as, for example, cars, trucks,all-terrain vehicles (ATVs), motorcycles, recreational vehicles (RVs),snowmobiles, boats, autonomous vehicles, semi-autonomous vehicles,industrial vehicles (e.g., construction vehicles), “riding” lawnmowers,planes, and/or any kind of land-, water-, or air-based vehicle.

“Vehicle user,” as used herein, may refer generally to a person who isresponsible for the vehicle, and who has access to use of the vehicle.Vehicle users may include owners, lessors, and/or renters, for example,of a vehicle. Vehicle users may also refer generally to the users of thevehicle that have agreed to pay a portion of vehicle costs associatedwith the vehicle.

“Trip,” as used herein, may refer generally to one complete use of thevehicle, from a starting point to an ending point. In some cases, thetrip may commence when the vehicle is started and may terminate when thevehicle is turned off. If a trip is defined in this way, the vehicle mayautomatically track and record trips, as commencement and terminationare simply defined. In other cases, the trip may be “manually” defined,such that a user designates a commencement and termination of a trip(e.g., when the vehicle may be turned on and off more than once in asingle user of the vehicle). In such cases, the vehicle may prompt theuser to designate the commencement and termination (e.g., using a userinterface of the vehicle and/or using an app available on a usercomputing device) of the trip such that the vehicle may track and recordthe trip.

“App,” as used herein, may refer generally to a software applicationinstalled and downloaded on a user interface of the vehicle and/or auser computing device associated with a vehicle user. An app associatedwith the shared vehicle system, as described herein, may be understoodto be maintained by the shared vehicle system and/or one or morecomponents thereof. Accordingly, the “maintaining party” of the app maybe understood to be responsible for any functionality of the app and maybe considered to instruct other parties/components to perform suchfunctions via the app. In the exemplary embodiment, the app enablesand/or requires the user computing device on which the app is installedand/or downloaded to pair with the vehicle (e.g., using a wirelessconnection, such as a Bluetooth® connection, or any other connection).“Pairing,” as used herein, may refer generally to registering aconnection between the vehicle and a user computing device such that theuser computing device may be recognized by the vehicle as thatparticular user computing device, and/or such that the user computingdevice may communicate with the vehicle (e.g., to input information tothe vehicle and/or receive information from the vehicle). “Dispute,” asused herein, may refer generally to any challenge or disagreement withany portion of the vehicle costs that are allocated to a vehicle user.

Asset Costs

“Asset costs” may be associated with the actual vehicle itself, and howthe vehicle users are permitted to use the vehicle. For example, assetcosts may include lease costs, purchase costs (e.g., down paymentsand/or monthly payments), and/or rental costs. Asset costs may bedetermined according to a provider of the vehicle (e.g., a cardealership or rental provider). Asset costs may be divided and/orallocated to vehicle users, according to one or more agreed-upon vehiclepolicies.

In some embodiments, according to a particular vehicle policy, assetcosts may be divided and allocated evenly between all vehicle users. Insuch cases, each vehicle user pays equally for the same access to,privilege of, and responsibilities for the vehicle. In otherembodiments, accordingly to another vehicle policy, asset costs may bedivided and allocated based upon actual usage of the vehicle by eachvehicle user. As one example, each vehicle user may pay a percentage ofthe asset cost that is proportional to the amount they use the vehicle(e.g., in terms of time, mileage, etc.). As another example, eachvehicle user may pay a portion of the asset cost according to theirprimary use type of the vehicle. In such cases, a vehicle user, User A,who uses the vehicle every week day, for commuting to and from work, maypay a higher portion of the asset cost than another vehicle user, UserB, who uses the vehicle only on weekends for recreational purposes.Because User A is more reliant upon the vehicle, User A may agree to avehicle policy in which they pay a higher portion of the asset cost.

Insurance Costs

“Insurance costs” may be associated with an insurance policy associatedwith use of the vehicle, and may be typically determined based upon arisk level associated with driver(s) of the vehicle. Insurance costs maybe determined by an insurance provider of the insurance policy anddivided and/or allocated to vehicle users, according to one or moreagreed-upon vehicle policies associated with insurance costs.

In some embodiments, according to a particular vehicle policy, insurancecosts may be divided and allocated evenly between all vehicle users.Insurance costs, in such cases, may be determined by the system basedupon an average risk level attributable to all vehicle userscollectively. In these embodiments, the vehicle user with the highestassociated individual risk level may benefit unduly, as their share ofthe risk that contributes to the insurance cost is being shared betweenall vehicle users. Likewise, the vehicle user with the lowest associatedindividual risk level may be disadvantaged, as they may pay more of aninsurance cost than they would if only their individual risk level weretaken into account.

In other embodiments, according to other vehicle policies, differentdivisions and allocations of insurance costs are contemplated. In afirst exemplary vehicle policy, each vehicle user may pay a percentageof the total insurance cost that is attributable to their respectiveshare of the risk level. Take a set of three vehicle users, forinstance. User A is a relatively low-risk driver and contributes only20% of the total risk level for the set of vehicle users. User B is amoderate-risk driver and contributes 30% of the total risk level. User Cis high-risk driver and contributes 50% of the total risk level. In thisfirst example vehicle policy, regardless of any actual usage, User Apays 20% of the total insurance cost, User B pays 30% of the totalinsurance cost, and User C pays 50% of the total insurance cost.However, in such cases, User C may be disadvantaged if their actualusage of the vehicle is much less than that of User A and/or User B.

As a second exemplary vehicle policy, insurance costs may be split basedupon actual usage, such as which vehicle user is driving the vehicle.Taking the same set of vehicle users described above, having a trip inwhich User A is driver may reduce the insurance cost associated withthat trip. For such trips, the insurance costs associated with the tripmay be divided and allocated evenly between all vehicle users present onthe trip. For example, Users A, B, and C may each pay an equal portionof the insurance cost for the trip, wherein the insurance cost iscalculated based upon User A acting as the driver. For such trips, theoverall insurance cost divided and allocated between the set of vehicleusers may be reduced, because of User A's comparatively low risk. User Amay accordingly be a driver on comparatively more trips, to maintain areduced insurance cost for the set of vehicle users. However, in such anexample, Users B and C may benefit unduly at least in part because theyare driving much less, and may be getting these low insurance costs fortrips that they share (as passengers) with User A (as the driver).Accordingly, the set of vehicle users may agree upon a vehicle policy inwhich Users B and C may pay a slightly higher portion of other vehiclecosts (e.g., fuel and/or maintenance costs) for each trip in which theyare passengers while User A is driving.

Another exemplary vehicle policy may be directed to usage-basedinsurance costs determined either before and/or after a trip is taken.Usage-based insurance costs may be determined based upon characteristicsof an insurance policy associated with the vehicle and/or with one ormore vehicle users. For example, in some cases, an insurance policy maydescribe insurance costs incurred based upon a number of miles drivenand/or an amount of time driven (e.g., based in part upon vehicletelematics data collected during a trip). In these cases, certainpremiums may apply to mileage driven and/or time driven below a certainthreshold, and other, greater premiums may apply to mileage drivenand/or time driven above that threshold. In other cases, the samepremium may apply to all mileage and/or time driven, for example, on apay-by-mile basis. Individual insurance policies associated with thevehicle and/or with each vehicle user may be retrieved and processed todetermine the insurance rate applied based upon a risk profile of thedriver, as discussed above, and an insurance rate applied based upon thetype and/or duration of a trip.

Fuel Costs

“Fuel costs” may be associated with fuel consumption by a vehicle andthe corresponding refueling. “Fuel” may refer generally to any kind offuel consumed by a vehicle, such as unleaded gas, diesel fuel,electricity, hydrogen, etc. Corresponding refueling costs mayaccordingly refer to gas/diesel prices, electric rates, fuel cells, etc.Fuel costs may be divided and/or allocated to vehicle users, accordingto one or more agreed-upon vehicle policies associated with fuel costs.

In one exemplary vehicle policy, fuel costs may be divided and allocatedequally between each vehicle user. Such a vehicle policy may more likelybe agreed upon by a set of vehicle users that typically use the vehicleat substantially equal rates. It will be understood that such a vehiclepolicy may be undesirable to a set of vehicle users in which one vehicleuser consumes the most fuel (e.g., uses the vehicle the most and/ordrives the furthest). Such a vehicle policy may additionally oralternatively be undesirable to a set of vehicle users in which onevehicle user consumes considerably less fuel than the one or more othervehicle users in the set.

Accordingly, in another exemplary vehicle policy, fuel costs may bedivided and allocated based upon actual usage. In such an embodiment,trip distances, times, and/or fuel usage may be tracked and recoded bythe system (e.g., as vehicle telematics data). In some embodiments, tripdistance may be tracked by retrieving an odometer reading at thebeginning and at the end of a trip. Trip distance and/or time mayadditionally or alternatively be tracked by receiving a GPS signal(e.g., transmitted to the vehicle and/or to a user computing devicewithin the vehicle) associated with the trip. Trip time may be trackedby determining a start-up time and a power-down time associated with thevehicle (e.g., when a user starts the ignition and when a user turns offthe engine, for a gas-powered car). Fuel usage may be tracked bydetermining a starting fuel level associated with a beginning of thetrip and an ending fuel level associated with the end of a trip. In someembodiments, the vehicle may include a fuel level sensor incommunication with the system, such that the system may retrieve fuellevel signals before, during, and/or after trips.

For each trip, at least one occupant vehicle user may be determined (asdescribed herein), recorded, and associated with the trip. The fuel costfor the trip may then be allocated to the one or more vehicle usersassociated with the trip. For example, if only one vehicle user isassociated with the trip, the entirety of the fuel cost for that tripmay be allocated to that one vehicle user. If two vehicle users areassociated with the trip, the fuel cost may be divided and allocatedbetween the two vehicle users. In some cases, the fuel cost may bedivided equally between the two vehicle users. In other cases, a“driver” vehicle user may have less of the fuel cost allocated theretoto “compensate” the driver for driving.

The system may determine the actual fuel cost by identifying a fuel typeassociated with the vehicle and a cost of that fuel at the time of thetrip. Alternatively, the system may determine relative percentages usedof the fuel of the vehicle based upon the trips associated with eachvehicle user, and may divide and allocate fuel cost to each vehicle userat the time of re-fueling. For example, for a gas-driven vehicle, thevehicle users may not refuel after each trip. At the time of refueling,one of the vehicle users may refuel the vehicle with 20 gallons of fuelat a cost of $40.00. Based upon the actual usage/fuel consumption of theset of vehicle users associated with the vehicle, User A consumed 50% ofthe fuel, User B consumed 25% of the fuel, and User C consumed 25% ofthe fuel. In one embodiment, according to one vehicle policy, User Awould have $20.00 of fuel cost allocated thereto, User B would have$10.00 of fuel cost allocated thereto, and User C would have $10.00 offuel cost allocated thereto.

Maintenance Costs

“Maintenance costs” may be associated with regular, scheduledmaintenance on the vehicle. “Regular” and/or “scheduled” may refergenerally to manufacturer-set or recommended maintenance schedules forvarious components of the vehicle. Without limitation, some examples ofmaintenance costs include costs associated with oil changes, air filterreplacement, replacement of wiper blades, and tire rotation and/oralignment. Maintenance costs may also be associated with legalmaintenance of ownership of the vehicle, such as vehicle-associatedproperty taxes, registration fees, title fees, etc. Maintenance costsmay be divided and/or allocated to vehicle users, according to one ormore agreed-upon vehicle policies associated with maintenance costs.

In one exemplary vehicle policy, maintenance costs (including legalmaintenance costs) may be divided and allocated equally between allvehicle users associated with the vehicle, because regular vehiclemaintenance may increase the longevity of the vehicle and, accordingly,may benefit all vehicle users equally. In another exemplary embodiment,certain maintenance costs, such as oil change costs, may be divided andallocated between vehicle users in accordance with their vehicle usage,because such maintenance may be correlated with vehicle usage (e.g., anoil change may be recommended every 3,000 miles).

Incidental Costs

“Incidental costs” may be associated with costs that may not fall intoany other category and may be further associated with specific and/orone-time events. Without limitation, some examples of incidental costsinclude costs associated with accidents, flat tires, highway tolls, andtickets. Incidental costs may be divided and/or allocated to vehicleusers, according to one or more agreed-upon vehicle policies associatedwith incidental costs.

In one exemplary vehicle policy, incidental costs may be divided andallocated equally between all vehicle users associated with the vehicle.These kinds of vehicle policies may be preferable to a set of vehicleusers who wish to share risk equally, such that no one vehicle user willbe penalized for one-time incidentals such as accidents. In anotherexemplary vehicle policy, certain incidental costs will be sharedequally, such as costs associated with an accident in which no vehicleuser was at fault (e.g., caused by another party), but other incidentalcosts will be allocated only to the vehicle user associated with thecorresponding incident, such as a toll cost incurred by one user drivingon the highway. In yet another exemplary vehicle policy, all incidentalcosts are allocated only to the vehicle user(s) associated with theincident in which the cost is incurred (e.g., even in the accidentreferenced above, only the vehicle user(s) in the vehicle at the time ofthe accident will have associated incidental costs of repair allocatedthereto).

Determining Occupants of the Vehicle

In at least some cases, the vehicle user that is acting as a driver fora trip in the vehicle may have a particular cost allocation associatedwith the driver role. For example, as described herein, insurance costsand/or incidental costs may be set and/or allocated in a particular waydepending upon which vehicle user is the driver for a trip. Accordingly,it may be beneficial to employ one or more methods of determining whichvehicle user is acting as the driver of the trip.

In the exemplary embodiment, the vehicle may include a communicationdevice that allows it to communicate with other devices, for example,via the Internet or any other wired or wireless connection (e.g.,Bluetooth®) over one or more radio links or wireless communicationchannels. In the exemplary embodiment, the vehicle may be incommunication with one or more user computing devices that are eachassociated with one of the vehicle users. In some embodiments, thevehicle may have “application pairing” functionality via thecommunication device, such that vehicle users may engage with an app ona user interface at the vehicle and/or on their user computing device(e.g., their smartphone). In one embodiment, at the beginning and/or atthe end of a trip, the app may prompt selection of which vehicle useris/was the driver of the trip, and the VCA computing device may recordthe selected driver as the driver for the trip. While this “honorsystem” embodiment may be relatively simple, it should be understoodthat it may invite errors, either intentional or unintentional. Errorsmay, in turn, invite disputes. Accordingly, this “honor system”embodiment may be supplemented and/or replaced by another method ofdetermining the driver of a trip.

Additionally or alternatively, this method may be employed as avalidation or verification to one or more other determination methods.For example, after a trip in which the driver is determined usinganother method, the app may prompt confirmation that the determineddriver was, in fact, the driver of the trip. The VCA computing devicemay receive an indication of a positive or negative response to theprompt, and update records for the trip accordingly. This confirmationmay serve to avoid disputes. Additionally or alternatively, this methodof manually selecting which vehicle user(s) are present in the vehicleduring the trip may be used by the VCA computing device to determinewhich, if any, other vehicle users are within the vehicle as passengersduring the trip (which may affect division and allocation of variousvehicle costs, as described herein).

Using the application pairing functionality, the VCA computing devicemay further determine which user computing device(s) are within thevehicle during a trip. For example, each user may pair one or more usercomputing devices (e.g., smartphones, tablets, laptops, wearables, etc.)to the vehicle. The vehicle may then pair with one or more usercomputing devices that are within the car during a trip. The vehicle mayrecord which device(s) pair with the vehicle for a trip and send anindication of such to the VCA computing device. If only one usercomputing device pairs with the vehicle, the VCA computing device mayrecord the vehicle user associated with that user computing device asthe driver for the trip. If more than one user computing device pairswith the vehicle, the VCA computing device may request selection and/orconfirmation of which associated vehicle user is the driver for thetrip, as described above (e.g., using an in-vehicle app and/or an app onthe user computing device). Additionally or alternatively, this methodof recording paired user computing devices may be used in determiningwhich, if any, other vehicle users are within the vehicle as passengersduring the trip (which may affect division and allocation of variousvehicle costs, as described herein).

In still other embodiments, the VCA computing device may use additionaland/or alternative vehicle telematics data, such as sensor informationfrom sensors within a paired user computing device, to determine whichvehicle user is the driver when multiple user computing devices pairwith the vehicle during a single trip. In one example, the VCA computingdevice may use gyroscope and/or accelerometer sensor information fromthe paired user computing devices to identify which side of the vehicleeach user of a user computing device used to enter the vehicle and/orexit the vehicle. In other words, the VCA computing device may accessand process data from the gyroscope and/or accelerometer for each usercomputing device to determine whether the user of the user computingdevice entered the vehicle on the left (e.g., driver) or the right(e.g., passenger). If only two user computing devices are present andthe VCA computing device determines that a first device is associatedwith the left side of the vehicle and a second device is associated withthe right side of the vehicle, the VCA computing device may record thatthe user associated with the first device is the driver and the user ofthe second device is a passenger for the trip. If more than one deviceis associated with the left side of the vehicle (e.g., the driver'sside), the VCA computing device may employ one or more other methodsdescribed herein to determine the driver of the vehicle. It should beunderstood that although the left side is associated with a “driver'sside” and the right side is associated with a “passenger side” herein,as is the custom in the United States of America, this method is easilyapplied to other driving customs in which the left side is a passengerside and the right side is the driver's side.

Another method of determining the driver of a trip may include providingvehicle user-specific keys. When the vehicle is obtained by the set ofvehicle users, each may receive a user-specific key fob (or otherdevice, such as a mobile device, i.e., smartphone or wearableelectronics), which is registered to that specific user. The vehicleusers may sign a contract or other agreement that each vehicle user willonly use the key specific to his- or herself, which may encourage thevehicle users to carefully and consistently only use their specific key.When the user-specific key is employed to unlock and/or start thevehicle (e.g., in keyless start vehicles), the vehicle may record whichkey is used, and, therefore, may indicate to the VCA computing devicewhich vehicle user to designate as the driver for the trip. Additionallyor alternatively, location-sensitive tracking may be used to determinewhich user-specific key is within the vehicle during the trip. If onlyone user-specific key is sensed, the vehicle may record whichuser-specific key was sensed, and the VCA computing device mayautomatically designate the associated vehicle user as the driver. Thislocation-sensitive tracking may be further used in determining which, ifany, other vehicle users are within the vehicle as passengers during thetrip (which may affect division and allocation of various vehicle costs,as described herein).

Moreover, in some embodiments, the vehicle and/or a paired usercomputing device may be configured to track driving characteristics ofthe vehicle and/or the driver of the vehicle during the trip.Additionally or alternatively, a separate computing device may beprovided for use with the vehicle (e.g., may be “plugged in” orotherwise coupled to the vehicle) that tracks driving characteristics.“Driving characteristics” may include, for example (but not limited to),sudden acceleration/deceleration, average speed, average stoppingdistance, and driving efficiency, as well as times the vehicle isdriven, distance driven, and/or location information of the trip. Usingthe manual user selection method, the paired-device method, and/or theuser-specific key method(s) described above, the VCA computing devicemay associate certain trips with specific vehicle users until drivingcharacteristics may be associated with particular vehicle users. The VCAcomputing device may employ machine learning functionality to developand maintain “driver profiles” for each of the vehicle users, such thatthe VCA computing device may use the driver profiles to identify whichvehicle user is the driver for future trips. For example, driving 15miles in the morning at average speeds of 50 mph and with few suddendecelerations may be associated with User A (e.g., a commuting user) fora dozen trips using one or more of the above methods, such that anyother trips that share some or all of these characteristics may beautomatically associated with User A (e.g., without using any or all ofthe above methods).

In still other embodiments, the vehicle may include and employ one ormore biometric sensors to determine which vehicle user is the driver fora trip. Biometric sensors may include any sensor configured to receive abiological signal uniquely identifying an individual, such as, but notlimited to, retinal scanners, fingerprint scanners, facial recognitiondevices, and weight scales. In one example, the vehicle may have one ormore fingerprint scanners on a component of the vehicle only easilyaccessible by the driver, such as the dashboard, the console or thesteering wheel. In another example, the vehicle may have a weight scale(or pressure sensor) associated with the driver's seat and/or with thepassenger's seats. The vehicle may have a registered weight associatedwith each vehicle user. When any vehicle user sits in any of the seats,their weight may be measured by the scale and the particular vehicleuser may be identified. The VCA computing device may then record theposition of each vehicle user within the vehicle for a trip, todetermine which vehicle user is the driver and/or a particularpassenger.

In some embodiments, if the VCA computing device is unable to determinewhich vehicle user is a driver, when more than one vehicle user is knownto be in the vehicle during a trip (e.g., by determining that more thanone user computing device paired with the vehicle during the trip), theVCA computing device may equally divide all costs associated with thetrip to each of the more than one vehicle users.

EXEMPLARY EMBODIMENTS

A vehicle cost allocation system for vehicles with shared ownership,usage, and/or costs may be provided. The amount of shared usage or costsmay be determined based upon vehicle and/or telematics data (which mayinclude vehicle trip, miles, GPS, vehicle operation and other types ofvehicle telematics data). For instance, several users may live in thesame community or apartment building, and collectively own or lease anautonomous vehicle for use by all of the users in the group.

In one aspect, an Application (“App”) may be built that tracks vehicleuse for each of the joint owners/lessees. The App may be employed on avehicle controller of a smart, semi-autonomous, or autonomous vehicle,and/or be employed on each user's mobile device within a group ofvehicle owners or lessees. Lease payments and insurance payments for thecollectively owned or leased vehicle may be split accordingly based uponindividual drivers and/or passengers in the vehicle for each trip.Insurance rates, including usage-based insurance rates and discounts,may be based upon driving history, usage, traditional insurance ratingfactors, and other telematics data (such as braking, acceleration,cornering, and other types of telematics data).

Billing may be embedded within the App, which may be installed on thevehicle or mobile devices of the owners/lessees. For instance, the Appmay support virtual billing and virtual financial account accounts.Additionally or alternatively, virtual bills may be sent separately withthe App used only to collect user, vehicle, and/or telematics data anddetermine costs.

Rates and payments based upon collective and/or individual vehicle usagemay prevent each of the joint owners or lessees from paying more thantheir fair share. Lease payments may be automatically be adjusted basedupon usage. Thus, risky driving by one of the joint owners may notimpact the insurance rates of the other joint owners in someembodiments.

When more than one owner is in the vehicle for a trip, incentives may begiven for letting the safest driver drive (to get the lowest rate permile). The insurance for a given trip may be usage-based insurance, anddetermined based upon the number of miles or length of trip, thelocation of the trip, the type of vehicle, the autonomous features ofthe vehicle, etc. The savings on the insurance costs and lease paymentsmay be split among all of the occupants to incentivize risk aversebehavior. That way, when carpooling, every occupant may have anincentive for the driver to drive safely.

Both lease payments and insurance payments may be adjusted to accountfor trips in which the vehicle is driven in an autonomous mode,especially if the autonomous mode is proven to be safer than humandriving.

Telematics data may be collected from various sources, including thevehicle, the smartphones or wearables of the lessees/drivers/passengers,and other external telematics data collection devices. Examples of dataelements include time driven, miles driven, occupants, and other roadtype and weather data.

Payments may be made semi-annually or automatically at the conclusion ofeach trip, including payments for usage-based insurance. Payments mayalso be made via an account with credit/debits for pay-by-the milepricing. Further, the App may display a list of trips, usage, and costsfor each lessee/owner. A joint account for all of the lessees/owners mayalso be set for gas, maintenance, oil changes, tirerotations/replacements, toll roads, parking, and other costs that may beused to pro-rate costs across lessees.

The present embodiments may offer (i) pro-rated insurance payments basedupon usage between joint owners from separate households using atelematics device; (ii) pro-rated lease payments based upon actualvehicle usage; and (iii) pro-rated vehicle costs based upon actualvehicle usage. The present embodiments also include providing incentivestailored to policyholders with shared ownership of a vehicle toencourage safer drivers to drive, as well as the use of provenautonomous driving features.

In one embodiment, a computer-implemented method for allocating vehiclecost between users of an autonomous vehicle may be provided. The methodmay be implemented using a vehicle cost allocation (VCA) computingdevice including a processor in communication with a memory. The methodmay include (1) receiving, via one or more processors, transceivers,and/or sensors (such as via wireless communication or data transmissionover one or more radio links or wireless communication channels), apotential trip report associated with a potential future trip to beperformed using an autonomous vehicle (such as from an autonomousvehicle transceiver or a user mobile device), the potential trip reportassociated with the autonomous vehicle and may include an identificationof an anticipated passenger, the potential trip report further includingan anticipated origination point and a destination point; (2)retrieving, via the one or more processors, (a) insurance policyinformation associated with the autonomous vehicle, and (b) autonomousfeature capabilities of the autonomous vehicle for a memory unit; (3)determining, via the one or more processors, a usage-based insuranceamount for the trip based upon (a) the potential trip report, (b) theinsurance policy information, and/or (c) autonomous feature capabilitiesof the autonomous vehicle; (4) transmitting, via the one or moreprocessors and/or transceivers, the usage-based insurance amount to theanticipated passenger's mobile device for review and/or acceptance;and/or (5) upon acceptance, allocating, via the one or more processors,the usage-based insurance amount to a financial account associated withthe anticipated passenger to facilitate sharing costs among joint ownersor lessees of autonomous vehicles. The method may include additional,less, or alternate actions, including those discussed elsewhere herein.

For instance, the method may include retrieving, via the one or moreprocessors, an identification of several joint owners or lessees of theautonomous vehicle from a memory unit; determining, via the one or moreprocessors, incidental costs for the trip; and/or allocating, via theone or more processors, the incidental costs among the several jointowners or lessees of the autonomous vehicle.

The method may include receiving, via the one or more processors,transceivers, and/or sensors, telematics data from the autonomousvehicle transceiver and/or a passenger's mobile device, the telematicsdata indicating operation and usage related data of the autonomousvehicle and/or autonomous features mounted thereon; and/or performing,via the one or more processors, one or more actions based upon thetelematics data. The one or more actions may include: updating, via theone or more processors, a risk profile for the autonomous vehicle basedupon the telematics data; and/or calculating, via the one or moreprocessors, a usage-based insurance rate, premium, or discount for theautonomous vehicle based upon the telematics data received associatedwith the autonomous vehicle.

In another embodiment, a computer system configured to allocate vehiclecost between users of an autonomous vehicle may be provided. Thecomputer system may include a vehicle cost allocation (VCA) computingdevice including a processor in communication with a memory. Thecomputer system may include one or more processors, transceivers, and/orsensors configured to: (1) receive, via wireless communication or datatransmission over one or more radio links or wireless communicationchannels, a potential trip report associated with a potential futuretrip to be performed using an autonomous vehicle (transmitted from anautonomous vehicle transceiver or a user mobile device), the potentialtrip report associated with the autonomous vehicle and including anidentification of an anticipated passenger, the potential trip reportfurther including an anticipated origination point and a destinationpoint; (2) retrieve (a) insurance policy information associated with theautonomous vehicle, and/or (b) autonomous feature capabilities of theautonomous vehicle for a memory unit; (3) determine a usage-basedinsurance amount for the trip based upon (a) the potential trip report,(b) the insurance policy information, and/or (c) autonomous featurecapabilities of the autonomous vehicle; (4) transmit the usage-basedinsurance amount to the anticipated passenger's mobile device for reviewand/or acceptance; and/or (5) upon receipt of acceptance, allocating,via the one or more processors, the usage-based insurance amount to afinancial account associated with the anticipated passenger tofacilitate sharing costs among joint owners or lessees of autonomousvehicles. The computer system may be configured with additional, less,or alternate functionality, including that discussed elsewhere herein.

For instance, the system may be configured to: retrieve anidentification of several joint owners or lessees of the autonomousvehicle from a memory unit; determine incidental costs for the trip;and/or allocate the incidental costs among the several joint owners orlessees of the autonomous vehicle.

The computer system may be further configured to receive telematics datafrom the autonomous vehicle transceiver and/or a passenger's mobiledevice, the telematics data indicating operation and usage related dataof the autonomous vehicle and/or autonomous features mounted thereon;and/or perform one or more actions based upon the telematics data. Theone or more actions may include: updating, via the one or moreprocessors, a risk profile for the autonomous vehicle based upon thetelematics data; and/or calculating, via the one or more processors, ausage-based insurance rate, premium, or discount for the autonomousvehicle based upon the telematics data received associated with theautonomous vehicle.

Other Considerations

It is contemplated that systems and methods described herein areapplicable equally to user-driven vehicles and self-driving orautonomous vehicles. Accordingly, vehicle users associated with aself-driving vehicle may have additional and/or alternative vehiclepolicies associated with self-driving capabilities of the self-drivingvehicle. For example, one vehicle policy may be associated with divisionand/or allocation of costs for times when the self-driving vehicle isunoccupied (e.g., when driving between homes of the vehicle users and/orfrom one vehicle user to another). Such “unoccupied” trips may havespecific and/or different costs associated therewith. For example,insurance costs may be lower for such trips (assuming a low accidentrate associated with the self-driving vehicle) or may be higher for suchtrips (assuming low confidence in an unoccupied vehicle), depending uponthe insurance policy associated with the vehicle. Fuel costs may belower for such trips, in such embodiments where the self-driving vehicledrives more efficiently than one or more of the vehicle users.

In one case, the vehicle users may agree upon a vehicle policy in whichall costs associated with these “unoccupied” trips are divided andallocated equally between them. In another case, the vehicle users mayagree upon a vehicle policy in which costs are divided and/or allocatedbetween users associated with the trip although not physically present.For example, if an unoccupied trip is driven between the home of User Ato the home of User B, both User A and User B may be associated withsuch a trip, as each is associated with one of the starting point andthe destination. The costs for such a trip (e.g., insurance and/or fuelcosts) may be thus be divided and allocated between User A and User B,but not between another User C.

Moreover, in some cases, certain liabilities associated with anunoccupied self-driving vehicle may be maintained by a vehiclemanufacturer associated with the self-driving vehicle. In such cases,the VCA computing device may reduce and/or eliminate certain costsassociated with unoccupied trips (e.g., reduce and/or eliminateinsurance costs).

In addition, one or more passenger vehicle users may be present during atrip driven by the self-driving or autonomous vehicle, as opposed tobeing driven by a human driver. In such embodiments, one vehicle policymay be associated with division and/or allocation of costs for timeswhen the self-driving vehicle is self- or vehicle-driven (i.e., notoperated by a human driver). Such “vehicle-driven” trips may havespecific and/or different costs associated therewith. For example,insurance costs may be lower for such trips (assuming a low accidentrate associated with the self-driving vehicle) or may be higher for suchtrips (assuming low confidence in a self-driven but occupied vehicle),depending upon the insurance policy associated with the vehicle. Fuelcosts may be lower for such trips, in such embodiments where theself-driving vehicle drives more efficiently than one or more of thevehicle users. Costs associated with vehicle-driven trips may be dividedand allocated (e.g., equally) between the vehicle user(s) present in thevehicle during the vehicle-driven trip.

As another consideration, it is contemplated that other people may driveand/or be present in the vehicle other than the vehicle users, such asspouses and/or children of the vehicle users. These people are referredto herein as “alternate users.” The vehicle users may agree upon one ormore vehicle policies associated with alternate users.

For example, one vehicle policy may require alternate users to be“registered” with a usage profile of the respective vehicle user withwhich they are associated (e.g., a child must be registered to the usageprofile of their parent(s)), such that costs of the alternate user maybe allocated to the associated vehicle user. The users may be requiredto provide their permission or affirmative consent for data collection,generation, and usage related to the embodiments discussed herein. Onevehicle policy may include adjustments to other vehicle policies in thecase of an alternate user driving the vehicle. For example, if ateenager is registered as an alternate user and carries a higherinsurance risk level, the parent vehicle user may have more of aninsurance cost allocated thereto than usual.

Another vehicle policy may strictly prohibit the driving of the vehicleby anyone other than a vehicle user.

The methods and system described herein may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware, or any combination or subset. As disclosedabove, at least one technical problem with current vehicle sharingsystems is that there is a need for enabling vehicle users to chooseexactly how they, as a group, want to split each particular kind ofvehicle cost. Without having vehicle policies specific to the vehicleusers, disputes may more easily arise, and some costs may go unpaid, asa result of those disputes and/or as a result of confusion that mayarise regarding each vehicle user's respective portion of the vehiclecosts. Moreover, many prior vehicle cost payees, such as insurancecompanies and/or vehicle manufacturers, may not be equipped to divideand allocate costs, especially when vehicle users agree upon complexvehicle policies regarding cost sharing, such as those based upon actualvehicle usage. A serious technical problem arises in determiningindividual vehicle user usage of the vehicle in order to implement theagreed-upon vehicle policies. More specifically, current cost-sharingsystems provide no way to determine which of the vehicle users areactually present on a trip and, therefore, are at least partiallyresponsible for the costs associated with that trip. In addition, thereis a need for a system configured to track and aggregate usage andassociated costs. The system and methods described herein address thattechnical problem.

The technical effect of the systems and processes described herein maybe achieved by performing at least one of the following steps, withvehicle owner or user permission or affirmative consent: (i) receiving aplurality of trip reports associated with a corresponding plurality oftrips performed using a vehicle within a predetermined interval of time,wherein each trip of the plurality of trips is associated with one ormore vehicle users of a plurality of vehicle users associated with thevehicle; (ii) generating a total vehicle usage report based at least inpart upon the plurality of trip reports, wherein the total vehicle usagereport describes the total usage of the vehicle by the plurality ofvehicle users over the interval of time; (iii) determining a totalvehicle cost associated with the vehicle over the interval of time basedat least in part upon the total vehicle usage report; (iv) generating arespective user usage report associated with each vehicle user of theplurality of vehicle users, based at least in part upon one or more tripreports of the plurality of trip reports associated with thecorresponding vehicle user; (v) determining a respective vehicle usercost attributable to each vehicle user of the plurality of vehicle usersbased at least in part upon the corresponding user usage report for thecorresponding vehicle user and the total vehicle cost; and/or (vi)allocating each respective vehicle user cost to the correspondingvehicle user.

The resulting technical effect is that the vehicle costs associated withuse and ownership of the vehicle are accurately and equitably (e.g.,according to the particular set of vehicle users) split between allvehicle users. When costs are divided and allocated according toexplicitly agreed-upon vehicle policies, the frequency of disputes overcost allocation may be reduced. A solution to the above-describedproblems provided by the system is determination of which vehicleuser(s) are associated with each trip such that vehicle policies may beimplemented by the system. The system includes a plurality of methodsfor determining occupants and/or a driver of a vehicle during a trip, asdescribed more fully herein. Some of these methods including usingsensor and/or biometric data, assessing other presence indicators suchas paired devices and/or user-specific keys, and requestingselection/verification of user presence from a vehicle user. Moreover,by managing payments using the systems and methods described herein, thevehicle users may be ensured precise and accurate payment of only theirshare of the vehicle costs.

Exemplary System

FIG. 1 depicts a schematic diagram of an exemplary shared vehicle system100. Shared vehicle system 100 is configured to enable tracking of tripsand costs associated with a vehicle 104 and divide and allocate thosecosts between one or more vehicle users associated with the vehicle 104and/or the trips. In one exemplary embodiment, system 100 may includeand/or facilitate communication between one or more vehicle costallocation (VCA) computing devices 102, a vehicle 104, a memory device108, one or more user computing devices 110 (each associated with arespective vehicle user, not shown), an insurance server 112, and one ormore financial institutions 114.

VCA computing device 102 may be any device capable of interconnecting tothe Internet, including a server computing device, a mobile computingdevice or “mobile device,” such as a smartphone, a personal digitalassistant (PDA), a tablet, a wearable device (e.g., a “smart watch” or apersonal projection device such as “smart glasses”), a “phablet,” orother web-connectable equipment or mobile devices. Components of system100 may be communicatively coupled to the Internet through manyinterfaces including, but not limited to, at least one of a network,such as the Internet, a local area network (LAN), a wide area network(WAN), or an integrated services digital network (ISDN), adial-up-connection, a digital subscriber line (DSL), a cellular phoneconnection, and a cable modem. In one embodiment, vehicle 104 mayinclude VCA computing device 102. In other words, VCA computing device102 may be located in vehicle 104.

Additionally, a database server 106 may be connected to memory device108 containing information on a variety of matters. For example, memorydevice 108 may include such information as trip reports, usage reportsassociated with respective vehicle users, rolling or progressive vehiclecosts, allocated costs associated with the respective vehicle users,vehicle policies, financial account and/or payment informationassociated with the respective vehicle users, paired user computingdevices, driving characteristics, dispute records, and/or any otherinformation used, received, and/or generated by shared vehicle system100, as described herein. In one exemplary embodiment, memory device 108may include a cloud storage device, such that information stored thereonmay be accessed by one or more components of shared vehicle system 100,such as, for example, VCA computing device 102, user computing device110, insurance server 112, and/or vehicle 104. In one embodiment, memorydevice 108 may be stored on VCA computing device 102. In any alternativeembodiment, memory device 108 may be stored remotely from VCA computingdevice 102 and may be non-centralized. Moreover, in any alternativeembodiment, memory device 108 may be stored on insurance server 112.

VCA computing device 102 may be in communication with vehicle 104, oneor more user computing device 110, insurance server 112, and/or one ormore financial institutions 114, such as via wireless communication ordata transmission over one or more radio frequency links or wirelesscommunication channels. In the exemplary embodiment, user computingdevices 110 may be computers that include a web browser or a softwareapplication to enable VCA computing device 102 and/or vehicle 104 toaccess user computing devices 110, and vice versa, using the Internet ora direct connection, such as a cellular network connection. Morespecifically, user computing devices 110 may be communicatively coupledto the Internet through many interfaces including, but not limited to,at least one of a network, such as the Internet, a local area network(LAN), a wide area network (WAN), or an integrated services digitalnetwork (ISDN), a dial-up-connection, a digital subscriber line (DSL), acellular phone connection, and a cable modem. User computing devices 110may be any device capable of accessing the Internet including, but notlimited to, a desktop computer, a mobile device (e.g., a laptopcomputer, a personal digital assistant (PDA), a cellular phone, asmartphone, a tablet, a phablet, netbook, notebook, smart watches orbracelets, smart glasses, wearable electronics, pagers, etc.), or otherweb-based connectable equipment. Additionally, user computing devices110 may be communicatively coupled to VCA computing device 102 and/orvehicle 104 through many interfaces including, but not limited to, adirect cable connection, a Bluetooth® connection, and a Wi-Ficonnection.

Vehicle 104 may include any kind of vehicle, such as, for example, cars,trucks, all-terrain vehicles (ATVs), motorcycles, autonomous vehicles,semi-autonomous vehicles, recreational vehicles (RVs), snowmobiles,boats, industrial vehicles (e.g., construction vehicles), “riding”lawnmowers, and/or any kind of vehicle. Generally, vehicles 104 will bedescribed herein using cars/trucks (e.g., personal vehicles) asexamples. However, these examples should not be construed to limit thedisclosure in any way, as the scope of the present disclosure may beapplicable to any kind of vehicle, including those listed hereinabove.In the exemplary embodiment, vehicle 104 includes a communication device(not shown in FIG. 1) such that vehicle 104 may communicate with VCAcomputing device 102, user computing devices 110, memory device 108,and/or insurance server 112, for example, via the Internet. Vehicle 104may further include a user interface (not shown in FIG. 1) such thatvehicle users of vehicle 104 may access certain features of vehicle 104(e.g., the communication device, one or more apps, “infotainment”features, climate control, etc.).

As described herein, vehicle 104 may be associated with a plurality ofvehicle users that share one or more costs associated with vehicle 104,in exchange for use of vehicle 104. For example, the vehicle users maybe co-owners, co-lessees, and/or co-renters of vehicle 104. The vehicleusers may agree upon one or more vehicle policies that describe howcosts will be divided and allocated between one another, variousexamples of which are provided herein.

In some embodiments, VCA computing device 102 may be associated with acost allocation service. Vehicle users may register or sign up with thecost allocation service to access the cost allocation functionality ofVCA computing device 102. In some embodiments, VCA computing device 102may be associated with an insurance company (e.g., associated withinsurance server 112). Vehicle users may be provided the cost allocationfunctionality of VCA computing device 102 upon purchasing an insurancepolicy associated with vehicle 104. In some embodiments, VCA computingdevice 102 is associated with a manufacturer, seller, lessor, and/orrental agency of vehicle 104, such that vehicle users may be providedthe cost allocation functionality of VCA computing device 102 uponpurchasing, leasing, and/or renting vehicle 104.

Vehicle users may transmit their agreed-upon vehicle policies to VCAcomputing device 102. VCA computing device 102 may process the vehiclepolicies and store the vehicle policies in memory device 108. In someembodiments, VCA computing device 102 may be configured to divide andallocate every vehicle cost associated with vehicle 104 on behalf of thevehicle users. In other embodiments, VCA computing device 102 may beconfigured to divide and allocate less than all of the vehicle costsassociated with vehicle 104, as decided upon by one or more vehicleusers. For example, vehicle users may request that VCA computing device102 divide and allocate all vehicle costs associated with actual usageof the vehicle (e.g., fuel costs, insurance costs, etc., in someexamples), but not any vehicle costs that will be split evenly betweenthe vehicle users (e.g., maintenance costs, in some examples). It shouldbe understood that VCA computing device 102 may be configured to divideand allocate any combination of vehicle costs associated with vehicle104.

In some embodiments, VCA computing device 102 may be further configuredto manage payment(s) of one or more vehicle costs on behalf of thevehicle users. In such embodiments, each vehicle user may maintain apayment account associated with the cost allocations services of VCAcomputing device 102, as described herein. VCA computing device 102 maywithdraw and/or cause withdrawal of funds in amounts corresponding tothe respective allocated portions of vehicle costs. VCA computing device102 may further transfer and/or cause transfer of those funds to one ormore parties associated with the vehicle costs (e.g., an insuranceprovider associated with the insurance cost, a car dealership orfinancial institution 114 associated with asset costs, a repair shopassociated with a maintenance cost, etc.). In some embodiments, VCAcomputing device 102 may alternatively withdraw funds in amountscorresponding to the respective allocated portions of vehicle costs andtransfer those funds to one financial account (e.g., maintained at afinancial institution 114 associated with VCA computing device 102), andmay further cause payments to be made to other parties from that onefinancial account.

In other embodiments, the vehicle users maintain respective paymentaccounts at respective financial institutions 114. VCA computing device102 may be configured to transmit instructions to each financialinstitution 114 to transfer the amount of funds corresponding to therespective vehicle user's portion of one or more vehicle cost(s) to afinancial institution 114 associated with that one or more vehiclecost(s). In still other embodiments, VCA computing device 102 may divideand allocate vehicle costs between the vehicle users, as describedherein, and transmit a message to each vehicle user (e.g., to a usercomputing device 110 associated therewith) indicating the respectiveamounts of each vehicle cost to be paid by that vehicle user to anassociated party. In other words, VCA computing device 102 may notmanage the transfer of funds but may indicate to the vehicle users howmuch they are obliged to pay each party according to their vehiclepolicies.

Financial institution 114 may include any financial institutionassociated with any component of system 100, one or more vehicle users,and/or a party to which payment is owed according to the vehicle cost(s)associated with vehicle 104. For example, financial institution 114 mayinclude a bank, at which one or more payment account(s) is maintained,that payment account(s) associated with any component of system 100, oneor more vehicle users, and/or a party to which payment is owed accordingto the vehicle cost(s) associated with vehicle 104.

Insurance server 112 may be associated with and/or maintained by aninsurance provider, which provides an insurance policy associated withvehicle 104. Insurance server 112 may communicate with VCA computingdevice 102, vehicle 104, user computing device(s) 110, and/or memorydevice 108 in order to transmit and/or receive information associatedwith the insurance policy. For example, insurance server 112 maytransmit insurance cost information associated with the respectivevehicle users to VCA computing device 102. As another example, insuranceserver 112 may retrieve usage report information from memory device 108to analyze the driving characteristics and/or other usage information ofone or more vehicle users, for example, to update an insurance policyassociated with vehicle 104.

Exemplary Vehicle Cost Allocation Computing Device

FIG. 2 depicts a schematic diagram of an exemplary VCA computing device102 (as shown in FIG. 1). In one exemplary embodiment, VCA computingdevice 102 may include a processor 202, a display device 204, acommunication device 206, and a memory 208 (which may be similar tomemory device 108, shown in FIG. 1). Processor 202 may be configured toexecute a plurality of modules, as described further herein.

Display device 204 may be configured to display output from processor202. Display device 204 may include a physical display device (e.g., ascreen or monitor) and/or may include computer-executable instructionsthat, when executed, cause display of a virtual user interface, forexample, at a user computing device 110 (shown in FIG. 1). In otherwords, display device 204 may include functionality to display an app,including an interactive user interface, at another computing device, toenable input to VCA computing device 102 as well as display of outputfrom VCA computing device 102.

Communication device 206 may be any device configured to enablecommunication between VCA computing device 102 and any other computingdevice (e.g., user computing device 110, vehicle 104, etc.) over a wiredor wireless connection. Communication device 206 may include, forexample, a wired or wireless network adapter and/or a wireless datatransceiver for use with a mobile telecommunications network.

Memory 208 may be configured to store information, such as, for example,vehicle policies 210, usage reports 212, trip reports 214, and/or paireddevice records 216. Vehicle policies 210 may be received and/or storedduring and/or after a registration phase, in which all vehicle usersagree upon each vehicle policy 210. Each vehicle policy 210 describeshow the vehicle users have agreed to handle, divide, allocate, and/orotherwise manage vehicle costs. Usage reports 212 may be generated andstored by, for example, vehicle usage analysis module 218, as describedfurther herein.

In one exemplary embodiment, VCA computing device 102 may receive tripreports 214 from vehicle 104 and/or one or more user computing devices110 (both shown in FIG. 1). Each trip report 214 may be associated witha trip performed using vehicle 104. Trip reports 214 may be associatedwith trips performed within a predetermined interval of time, such as,for example, a billing period, a month, two months, two weeks, or anyother interval of time. Each trip described in a trip report 214 may befurther associated with one or more of the vehicle users associated withvehicle 104. VCA computing device 102 may receive paired device records216 from, for example, vehicle 104. Paired device records 216 may refergenerally to reports of which paired devices (e.g., user computingdevices 110) paired with vehicle 104 during a trip and/or indications ofwhich vehicle user is associated with each paired device. It should beunderstood that memory 208 may be configured to store more, less, and/ordifferent information, including any other information described herein.

In one exemplary embodiment, processor 202 may include a vehicle usageanalysis module 218, an occupant determination module 220, a driverdetermination sub-module 221, a cost allocation module 222, and apayment management module 224. It should be understood that thesemodules are illustrative only, and that any of the functionality of anymodule described herein may be performed by any other module and/or begenerally performed using processor 202.

In one embodiment, VCA computing device 102 may receive a request forusage analysis, the request including vehicle data identifying vehicle104 from which VCA computing device 102 may identify the vehicle usersassociated with vehicle 104. Vehicle usage analysis module 218 mayaccess trip reports 214 and vehicle policies 210 to generate a totalvehicle usage report. The total vehicle usage report describes the totalusage of vehicle 104 by the vehicle users over the interval of time. Inother words, vehicle usage analysis module 218 may develop a report ofthe total usage of vehicle 104, including, for example, time driven,fuel used, any maintenance performed, mileage driven, types of trips,etc. Based at least in part upon the total vehicle usage report, vehicleusage analysis module 218 may determine a total vehicle cost associatedwith vehicle 104 over the interval of time. The total vehicle cost mayinclude a total of all types of costs, including asset costs, fuelcosts, maintenance costs, insurance costs, and/or incidental costs.

In some embodiments, to generate the total vehicle usage report anddetermine the total vehicle cost, vehicle usage analysis module 218 mayprocess and analyze individual trip reports 214 (and associated costs),and aggregate the results of that analysis to generate the total vehicleusage report. Vehicle usage analysis module 218, for a single tripreport 214, may determine a time/mileage traveled and/or locationstraveled between, for example, to determine a corresponding amount offuel used and, thus, a fuel cost associated with the trip. Vehicle usageanalysis module 218 may also retrieve any maintenance and/or incidentalreports (not specifically shown) stored in memory 208 and associatedwith a particular trip and/or with vehicle 104 in general, for example,to determine maintenance costs and/or incidental costs for a trip and/orfor the interval of time. Vehicle usage analysis module 218 may alsodetermine, for a single trip report 214, a usage type of the trip (e.g.,road trip vs. errand vs. commute), and/or one or more vehicle user(s)and/or a driver associated with the trip (e.g., by communicating withoccupant determination module 220), for example, to determine insurancecosts and/or other costs associated with each trip.

Vehicle usage analysis module 218 may be configured to determine certaincosts on a per-trip and/or per-interval (e.g., “total”) basis. Forexample, in some embodiments, vehicle usage analysis module 218 maydetermine a fuel cost associated with each particular trip. Vehicleusage analysis module 218 may parse the trip report 214 for a distancetraveled and/or fuel usage, and may calculate a fuel cost for thatassociated trip based upon a current fuel price. In some embodiments,vehicle usage analysis module 218 may access external database(s) and/orother sources of information to determine a current fuel price.

In some embodiments, vehicle usage analysis module 218 determines atotal fuel cost for the entire interval, for example, by requesting amileage and/or fuel report from vehicle 104. Vehicle 104 may generateand transmit a mileage and/or fuel report by accessing sensor data from,for example, an odometer and/or fuel sensor, respectively. In stillother embodiments, vehicle usage analysis module 218 may determine afuel cost for the interval based upon reported fuel costs and/orpayments. Reported fuel payments may be transmitted to VCA computingdevice 102 by, for example, a vehicle user. The vehicle user maytransmit a fuel cost payment receipt to VCA computing device 102, maydesignate one particular payment method as a fuel cost payment method(e.g., a particular credit or debit card used only for payment of fuelcosts, which may be accessible and/or usable by all vehicle users and/ormay be associated with an individual or joint financial accountassociated with one or more vehicle users), and/or may transmit anyother indication of a fuel cost payment and/or fuel cost bill to VCAcomputing device 102.

Similarly, vehicle usage analysis module 218 may determine incidentalcosts for the interval based upon reported incidental payments. Reportedincidental payments may be transmitted to VCA computing device, forexample, by a vehicle user. The vehicle user may transmit an incidentalcost payment receipt (e.g., a repair bill or toll cost) to VCA computingdevice 102, may designate one particular payment method as an incidentalcost payment method (e.g., a particular credit or debit card used onlyfor payment of incidental costs, which may be accessible and/or usableby all vehicle users and/or may be associated with an individual orjoint financial account associated with one or more vehicle users),and/or may transmit any other indication of an incidental cost paymentand/or incidental cost bill to VCA computing device 102.

As another example, vehicle usage analysis module 218 may determinemaintenance costs for the interval based upon maintenance costs invoicesor reports submitted to VCA computing device 102 (e.g., by one of thevehicle users). Vehicle usage analysis module 218 may additionally oralternatively determine an expected maintenance cost based upon anaverage maintenance cost for that vehicle 104 over the interval. In someembodiments, vehicle usage analysis module 218 may access externaldatabase(s) and/or other sources of information to determine an averagemaintenance cost for vehicle 104 over a particular interval of time. Asyet another example, vehicle usage analysis module 218 may determineasset costs for the vehicle 104 based upon one or more monthly paymentsrequested by an asset payee (e.g., a car dealership or automanufacturer).

Occupant determination module 220 may be configured to determine whichof the vehicle users associated with vehicle 104 are associated with aparticular trip. For example, occupant determination module 220 may beconfigured to determine which of the vehicle users were present invehicle 104 during the trip. In one embodiment, vehicle usage analysismodule 218 requests performance of such determination, for example, bytransmitting a trip report 214 to occupant determination module 220.Occupant determination module 220 may include a driver determinationsub-module 221. When occupant determine module 220 determines that morethan one vehicle user is present in vehicle 104 during a trip, occupantdetermine module 220 may employ driver determination sub-module 221 todetermine which of those present vehicle users was the driver for thetrip. In at least some cases, the vehicle user that is acting as adriver for a trip in vehicle 104 may have a particular cost allocationassociated with the driver role. For example, insurance costs and/orincidental costs may be set and/or allocated in a particular waydepending on which vehicle user is the driver for a trip. Anyfunctionality described with respect to occupant determination module220 may be performed by driver determination sub-module 221, and viceversa.

Occupant determination module 220 may, in one embodiment, employ a “userselection” method of occupant and/or driver determination. In such anembodiment, at the beginning and/or at the end of a trip, underinstruction from VCA computing device 102 via the app, vehicle 104 mayprompt user selection of one or more vehicle user(s) are present invehicle 104 for the trip and which vehicle user is/was the driver of thetrip. For example, vehicle 104 may display the app at a user interfaceof vehicle 104 and display such a prompt therein. Vehicle 104 mayreceive input of the user selection, which identifies the selectedvehicle users present on the trip and/or the selected driver, and appendthe user selection to the trip report 214 associated with that trip.Occupant determine module 220 may then parse the trip report 214 for theuser selection and determine the vehicle users identified in the userselection to be the vehicle users associated with the trip. Where adriver vehicle user is identified, driver determination sub-module 221may determine the driver vehicle user identified in the user selectionto be the driver of the trip.

Additionally or alternatively, occupant determination module 220 mayemploy this “user selection” method as a validation or verification toone or more other determination methods. For example, after a trip inwhich the driver is determined using another method, under instructionfrom VCA computing device 102 via the app, vehicle 104 and/or one ormore user computing devices 110 may prompt confirmation that the vehicleusers determined to be present were, in fact, present on the trip and/orthat the determined driver was, in fact, the driver of the trip. Vehicle104 and/or user computing device 110 may receive an indication, via theapp, of a positive or negative response to the prompt, and append thetrip report 214 associated with the trip to include the response.

Occupant determination module 220 may additionally or alternatively takeadvantage of pairing functionality, via the app, between vehicle 104 anduser computing device(s) 110 associated with vehicle users. During atrip, vehicle 104 may pair with one or more user computing devices 110that are within vehicle 104. Vehicle 104 and/or user computing device(s)110 may generate one or more paired device records 216 associated withthe trip report 214 for that trip. Occupant determination module 220 mayaccess paired device records 216 associated with the trip report 214 anddetermine the vehicle user(s) associated with the paired user computingdevice(s) 110 identified in the paired device record 216 to be thevehicle user(s) associated with the trip. If only one paired devicerecord 216 is associated with the trip report 214, indicating that onlyone user computing device 110 paired with vehicle 104, driverdetermination sub-module 221 may determine the vehicle user associatedwith the single paired user computing device 110 to be the driver forthe trip. If vehicle 104 and/or user computing device(s) 110 generatemore than one paired device record 216 associated with a trip report214, vehicle 104 and/or the user computing device(s) 110 may, underinstruction from VCA computing device 102 via the app, request userselection of which vehicle user is the driver for the trip, as describedabove.

Occupant determination module 220 may additionally or alternatively takeadvantage of sensor data from sensors in vehicle 104 and/or usercomputing device(s) 110 (e.g., paired user computing device(s) 110). Inone example, user computing device(s) 110 may generate sensor data froma gyroscope and/or accelerometer sensor. User computing device(s) 110may transmit the sensor data to vehicle 104 and/or VCA computing device,and/or may append the sensor data to the trip report 214 for a trip,under instruction from VCA computing device 102 via the app. Occupantdetermination module 220 may analyze the sensor data to identify whichside of vehicle 104 each user of a respective user computing device 110used to enter vehicle 104 and/or exit vehicle 104. In other words,occupant determination module 220 may access and process the sensor datafrom the gyroscope and/or accelerometer for each user computing device110 to determine whether the user of the user computing device 110entered vehicle 104 on the left (e.g., driver) or the right (e.g.,passenger). If the trip report 214 and/or associated paired devicerecords 216 identify two user computing devices 110 present on a trip,and occupant determination module 218 uses the processed sensor data todetermine that one device 110 is associated with the left side ofvehicle 104 and a second device 110 is associated with the right side ofvehicle 104, occupant determination module 220 may record that thevehicle user associated with the first device 110 is the driver and thevehicle user of the second device 110 is a passenger for the trip. Ifmore than one device 110 is associated with the left side of vehicle 104(e.g., the driver's side), driver determination sub-module 221 mayemploy one or more other methods described herein to determine thedriver of the vehicle.

In another embodiment, vehicle 104 may generate sensor data using one ormore biometric sensors. Biometric sensors may include any sensorconfigured to receive a biological signal uniquely identifying anindividual, such as, but not limited to, retinal scanners, fingerprintscanners, facial recognition devices, and weight scales. For example,vehicle 104 may have one or more fingerprint scanners on a component ofthe vehicle 104 only easily accessible by the driver, such as thedashboard, the console or the steering wheel. In another example,vehicle 104 may have a weight scale associated with the driver's seatand/or with the passenger's seats. Occupant determination module 220 maystore a registered weight (or any other biometric marker) associatedwith each vehicle user. When any vehicle user sits in any of the seats,their weight may be measured by the scale and the particular vehicleuser may be identified. Under instruction from VCA computing device 102via the app, vehicle 104 may append to the trip report 214 anidentification of each vehicle user within vehicle 104 and/or anidentification of the position of each vehicle user within vehicle 104.Occupant determination module 220 may parse the trip report 214 for theidentification of each vehicle user within vehicle 104 and associatethose vehicle users with the trip. Driver determination sub-module 221may parse the trip report 214 for the identification of which vehicleuser was recorded in the driver position, and determine the driver forthe trip to be that vehicle user.

In some embodiments, vehicle 104 may include a plurality ofuser-specific keys. When vehicle 104 is obtained by the set of vehicleusers, each may receive a user-specific key fob (or other device), whichis registered to or otherwise specifically associated with that specificvehicle user. The vehicle users may sign a contract or other agreementthat each vehicle user will only use the key specific to his- orherself, which may encourage the vehicle users to carefully andconsistently only use their specific key. Under the instruction of VCAcomputing device 102 via the app, vehicle 104 may record whichuser-specific key is used to unlock and/or start vehicle 104 and appendan identification of that vehicle user and/or the user-specific key tothe trip report 214. Driver determination sub-module 221 may parse thetrip report 214 for the identification of the user-specific key and maydetermine that the associated vehicle user is the driver for that trip.Additionally or alternatively, vehicle 104 may include one or moresensors (e.g., one or more proximity sensors) configured to sense whichuser-specific key(s) is within the vehicle during the trip. If only oneuser-specific key is sensed, vehicle 104 may record which user-specifickey was sensed, and append an identification of that vehicle user and/orthe user-specific key to the trip report 214.

Moreover, in some embodiments, vehicle 104 and/or a user computingdevice 110 (e.g., a paired user computing device 110) may be configuredto track driving characteristics of vehicle 104 and/or the driver ofvehicle 104 during a trip. Additionally or alternatively, a separatecomputing device may be provided for use with the vehicle (e.g., may be“plugged in” or otherwise coupled to the vehicle) that tracks drivingcharacteristics. Driver determination sub-module 221 may use anyoccupant-determination method(s) described herein to associate certaintrips with specific vehicle users until driver determination sub-module221 may automatically associate driving characteristics with particularvehicle users. For example, driver determination sub-module 221 mayinclude machine learning functionality and may develop and maintain“driver profiles” for each of the vehicle users by using anyabove-described method to associate a vehicle user with particulardriving characteristics. Driver determination sub-module 221 may thenuse the driver profiles to automatically identify which vehicle user isthe driver in future trips (e.g., without using any or all of the abovedescribed driver determination methods).

When occupant determination module 220 makes an identification of anyand/or all vehicle users present in vehicle 104 during a trip, occupantdetermination module 220 may append an identification of each of thesevehicle users to the associated trip report 214. When driverdetermination sub-module 221 determines a driver for a trip, occupantdetermination module 220 may append an identification of the driver tothe trip report 214. In some embodiments, when driver determinationsub-module 221 is unable to determine which vehicle user is a driver,when more than one vehicle user is known to be in the vehicle during atrip, occupant determination module 220 may append a “driver unknown”indication with the trip report 214. In some embodiments, vehicle 104includes an autonomous or self-driving vehicle 104. Under instructionfrom VCA computing device 102 via the app, for any trip in which novehicle user is driving (e.g., an “autonomous trip”), vehicle 104 mayappend an indication to the associate trip report 214 that the trip isan autonomous trip. Occupant determination module 220 may additionallyappend a “no associated driver—autonomous trip” indication (or type orversion of autonomous vehicle system software driving the vehicle) totrip report 214.

Based upon the determined vehicle users associated with the trip,vehicle usage analysis module 218 may determine certain vehicle costsattributable to a trip. For example, vehicle usage analysis module 218may determine which vehicle users (i.e., the vehicle users associatedwith a trip) are associated with a particular incidental cost. Asanother example, vehicle usage analysis module 218 may be configured todetermine insurance costs associated with the trip, based upon vehiclepolicies 210 as well as insurance information associated with eachrespective vehicle user. Vehicle usage analysis module 218 may transmitinstructions to insurance server 112 (shown in FIG. 1) to communicateinsurance rates and/or other insurance information (e.g., insurancepolicy information) to vehicle usage analysis module 218.

In some embodiments, wherein vehicle 104 includes an autonomous vehicle104, this insurance information may include liability informationdescribing which party maintains liability when the autonomous vehicle104 is driving. For example, the manufacturer of the autonomous vehicle104 may maintain liability during such “autonomous” trips. Vehicle usageanalysis module 218 may use output from occupant determination module220 to identify trip reports 214 associated with autonomous trips.Vehicle usage analysis module 218 may indicate that no insurance costshould be associated with such autonomous trips, in embodiments in whichinsurance costs are incurred on a per-trip basis.

Vehicle usage analysis module 218 generates and maintains a respectiveuser usage report 212 associated with each vehicle user, based at leastin part each trip report 214 associated with the corresponding vehicleuser (e.g., based upon the output from occupant determination module220). Each usage report 212 describes the cumulative amount, frequency,and/or type of usage of vehicle 104 by the respective vehicle user.

Cost allocation module 222 may be configured to use each usage report212 to determine a respective vehicle user cost (i.e., a portion of thetotal vehicle cost for the interval of time) attributable to eachvehicle user. Cost allocation module 222 may retrieve vehicle policies210 and, based upon the content and directives thereof, divide the totalvehicle cost amongst the vehicle users. Cost allocation module 222 maydivide and allocate certain “sub-costs” differently, in accordance withvehicle policies 210. For example, cost allocation module 222 may beconfigured to divide a total asset cost associated with vehicle 104during the interval of time evenly between all of the vehicle users.

Cost allocation module 222 may be configured to divide a total fueland/or maintenance cost associated with vehicle 104 during the intervalof time according to actual usage, based upon the respective usagereports 212. Cost allocation module 222 may be configured to determine atotal insurance cost associated with usage of vehicle 104 over theinterval of time, based upon usage reports 212 and/or insuranceinformation received from insurance server 112.

In some cases, insurance costs may vary on a per-trip basis based upon adriver of each trip. In other cases, insurance costs may be fixed on aper-interval basis (e.g., $X/month), based upon an average risk level ofall vehicle users. In other cases, insurance costs may be determinedbased upon usage of vehicle 104, and are accrued on a mileage- and/ortime-driven basis (e.g., on a “pay-by-mile” basis). Cost allocationmodule 222 may be configured to determine an insurance cost associatedwith a particular trip based upon mileage driven and/or time driven onthat particular trip. For example, cost allocation module 222 mayretrieve a trip report 214 that identifies the driver of the trip andone or more characteristics of the trip, such as mileage driven and/ortime driven. Cost allocation module 222 may process insuranceinformation associated with the driver and/or vehicle 104 to determinethe insurance cost associated with that particular trip according to aninsurance rate included in the insurance information and the mileagedriven and/or time driven.

In some embodiments, cost allocation module 222 is configured to receiveinformation (e.g., from vehicle 104 and/or a user computing device 110)about a potential trip to be taken using vehicle 104. This “potentialtrip report” may include an identification of the driver for the trip,any vehicle user passengers anticipated on the trip, and an estimatedmileage and/or trip to be driven. The estimated mileage and/or time maybe manually entered by a user (e.g., “100 miles”). Additionally oralternatively, the potential trip report may include an anticipateddestination for the potential trip. Cost allocation module 222 maydetermine the estimated mileage based upon a current location of vehicle104 and/or the user computing device 110 and the anticipated location(e.g., using GPS coordinates, a mapping/direction service, and/or usingany other method). Cost allocation module 222 may process the potentialtrip report and retrieve insurance information associated with theidentified driver from insurance server 112, to report an anticipatedinsurance cost for the trip back to vehicle 104 and/or the usercomputing device 110. Cost allocation module 222 may determine andreport other costs associated with the potential trip, such as a fuelcost and/or incidental costs (e.g., expected tolls), for example, byaccessing data related thereto (e.g., current fuel rates near thelocation of vehicle 104 and/or along an anticipated route). Costallocation module 222 may receive a response from vehicle 104 and/or theuser computing device 110 including (i) an affirmative response, thatthe vehicle user(s) will be taking the potential trip; (ii) a negativeresponse, that the vehicle user(s) will not be taking the potentialtrip; or (iii) an edit response, that includes one or more changes tothe potential trip report. Cost allocation module 222 may allocate thedetermined costs to each vehicle user identified in the potential tripreport and/or may place a “hold” on one or more financial accounts ofthe vehicle user(s) for the determined costs, as real trip costs maydiffer from pre-trip estimated costs.

Cost allocation module 222 may be configured to divide the totalinsurance cost based upon the insurance information, usage reports 212,and/or vehicle policies 210. Cost allocation module 222 may beconfigured to determine which trip reports 212 are associated withautonomous trips, in which insurance costs may vary and/or be eliminated(for the vehicle users) and may adjust a total insurance cost and/or arespective user portion of the total insurance cost accordingly. Forexample, cost allocation module 222 may remove an insurance cost portionfor each vehicle user associated with an autonomous trip.

Cost allocation module 222 may be further configured to allocate eachrespective vehicle user cost to the corresponding vehicle user. Eachvehicle user cost may include an aggregate of the vehicle user'sportions of each “sub-cost,” for example, a total amount including aportion of the total insurance cost, a portion of the total asset cost,a portion of the total fuel cost, etc. Additionally or alternatively,each vehicle user cost may include an itemized breakdown on aper-“sub-cost”, per trip, and/or usage percentage (of the total) basis.

Payment management module 224 may be configured to manage payments ofeach vehicle user cost, in accordance with one or more vehicle policies210 and/or in accordance with the wishes of the vehicle users. Thefunctionality of payment management module 224 is described furtherherein with respect to FIG. 4.

In some embodiments, display device 204 may be configured to facilitatedisplay of up-to-date trip reports 214, usage reports 212, and/or costsfor each vehicle user. For example, display device 204 may be configuredto display a “dashboard” within the app (e.g., on a user interface ofvehicle 104 and/or user computing device 110). Each vehicle user may“log-in” to the app to have displayed their own personal trip, usage,and/or costs data. Moreover, in some embodiments, display device 204 maybe configured to display bills, reminders, notifications, and/or otherinformation to each vehicle user within the app.

Exemplary Vehicle

FIG. 3 depicts a view of an exemplary vehicle 104 (shown in FIG. 1).Although vehicle 104 is illustrated as a car, it should be understoodthat vehicle 104 may include any other kind of vehicle, such as, but notlimited to, trucks, motorcycles, boats, planes, RVs, etc.

Vehicle 104 includes a plurality of sensors 302, a communication device304, and a vehicle computing device 306. The plurality of sensors 302may include, for example, biometric sensors, proximity-based sensors(e.g., for tracking paired/registered keys, key fobs, paired usercomputing devices 110, etc.), driving characteristic sensors (e.g.,accelerometers, gyroscopes, GPS devices, etc.) or telematics datacollection devices, and/or any other kind of sensor. Vehicle computingdevice 306 is configured to collect sensor data from sensors 302. Insome embodiments, vehicle computing device 306 may process, store,and/or transmit sensor data, including as described herein.

Vehicle computing device 306 may be any computing device capable ofperforming the functions described herein. Vehicle computing device 306may be integral to vehicle 104 (e.g., a console computing device) and/ormay be coupled to vehicle 104 (e.g., an after-market or retro-fitcomputing device). Moreover, it is contemplated that in someembodiments, vehicle computing device 306 may include VCA computingdevice 102 (shown in FIG. 1), such that the functionality of VCAcomputing device 102 may be performed at vehicle 104. Vehicle computingdevice 306 may be communicatively coupled to the Internet throughcommunication device 304. Additionally, vehicle computing device 306 maycommunicate with VCA computing device 102 and/or user computingdevice(s) 110 using communication device 304. Communication device 304may include, for example, a wired or wireless network adapter and/or awireless data transceiver for use with a mobile telecommunicationsnetwork. Communication device 304 may be configured to communicationusing many interfaces including, but not limited to, at least one of anetwork, such as the Internet, a local area network (LAN), a wide areanetwork (WAN), or an integrated services digital network (ISDN), adial-up-connection, a digital subscriber line (DSL), a cellular phoneconnection, a cable modem, a Wi-Fi connection, and a Bluetooth®connection.

In one embodiment, vehicle 104 includes a self-driving vehicle 104.Self-driving vehicle 104 may be an autonomous vehicle capable offulfilling the transportation capabilities of a traditional automobileor other vehicle. Self-driving vehicle 104 may be capable of sensing itsenvironment and navigating without human input. Self-driving vehicle 104may perform all safety-critical functions for the entire trip, with thedriver not expected to control the vehicle at any time. As thisself-driving vehicle 104 would control all functions from start to stop,including all parking functions, it may include unoccupied vehicles.

The plurality of sensors 302 in self-driving vehicle 104 may detect thecurrent surroundings and location of self-driving vehicle 104. Theplurality of sensors 302 may further include, but are not limited to,radar, LIDAR, Global Positioning System (GPS), and computer vision.Vehicle computing device 306 may interpret the sensory information toidentify appropriate navigation paths, as well as obstacles and relevantsignage. In some embodiments, vehicle computing device 306 may updatemaps based upon sensory input, allowing vehicle computing device 306 tokeep track of self-driving vehicle's 104 position, even when conditionschange or when self-driving vehicle 104 enters uncharted environments.Additionally, vehicle computing device 306 may control the direction andspeed of self-driving vehicle 104. Vehicle computing device 306 mayallow self-driving vehicle 104 to travel from point A to point B withoutinput from a human operator (e.g., a vehicle user). In the exemplaryembodiment, vehicle computing device 306 may direct self-driving vehicle104 with a human occupant (e.g., a vehicle user and/or a vehiclenon-user) in self-driving vehicle 104.

Exemplary Payment Management

FIG. 4 illustrates a data flow diagram 400 showing exemplaryfunctionality of VCA computing device 102 (shown in FIGS. 1 and 2). Morespecifically, FIG. 4 illustrates exemplary payment managementfunctionality of payment management module 224 (shown in FIG. 2) of VCAcomputing device 102. It should be understood that the functionalitydescribed herein is illustrative only and should not be construed tolimit the present disclosure.

In one exemplary embodiment, vehicle 104 (shown in FIG. 1) has aplurality of vehicle costs associated therewith, as described herein.Each vehicle cost may be paid to a different payee party. For example,in one embodiment, such payee parties may include, without limitation,an insurance provider (e.g., payee for an insurance cost), a cardealership (e.g., payee for an asset cost), a repair shop (e.g., payeefor a maintenance cost), and/or another vehicle user (e.g., a vehicleuser who paid a fuel cost upfront and is to be reimbursed by the othervehicle users). Payee parties may maintain respective financial accountsat financial institutions 114 (shown in FIG. 1). Accordingly, in FIG. 4,three payee parties are represented by their respective financialinstitutions 114.

In some embodiments, each payee party issues one bill covering theentirety of the vehicle cost associated with that party. For example, arepair shop may issue a single bill for $80 for an oil change. VCAcomputing device 102, as described above with respect to FIG. 2,determines what portion of this $80 is attributable to each vehicleuser. Payment management module 224 may then issue a “pseudo-bill” toeach vehicle user, the pseudo-bill indicating the respective portion ofthe $80 that must be paid by each vehicle user.

In one embodiment, each vehicle user may independently make a payment tothe payee party. Continuing with the above example, each vehicle usermay independently make a payment to the repair shop in an amountcorresponding to their portion of the $80 charge. In another embodiment,each vehicle user may pay one “representative” vehicle user, who willthen make one “lump” payment to the payee party.

In some embodiments, VCA computing device 102 automatically handlespayment of the payee party, in accordance with one or more vehiclepolicies 210 (shown in FIG. 2) and/or other instructions given by eachvehicle user. In some cases, one or some of a plurality of vehicle usersmay choose to use the payment management functionality of VCA computingdevice 102. In other cases, all of a plurality of vehicle users maychoose to use the payment management functionality of VCA computingdevice 102.

In one embodiment, payment may be rendered by each vehicle user on aprepayment schedule (e.g., whether payment is automatically managedusing payment management module 224 or manually by each vehicle user).In other words, payment for a particular interval (e.g., one month) maybe rendered prior to that interval (e.g., during the preceding month).However, this may pose some challenge for groups of vehicle users withvehicle policies 210 that divide one or more vehicle costs based uponactual usage.

In some embodiments, an equal division of all costs may be allocated forpre-payment for a number of “preliminary” intervals (e.g., the firstthree months of the cost-sharing structure implemented by the vehicleusers as set out in vehicle polices 210). During these preliminaryintervals, each vehicle user may pay equal portions of the vehicle costsbut actual usage may be tracked and recorded, as described herein. VCAcomputing device 102 may develop “average usage reports” (which mayinclude and/or be similar to usage reports 212, shown in FIG. 2) foreach individual vehicle user, for each vehicle policy and/or costcategory (e.g., average fuel use for each vehicle user, average numberof trips as a driver, etc.).

For the first interval after the preliminary intervals, portions of thevehicle costs may be allocated to each vehicle user according to theirrespective average usage report and vehicle policies 210. Actual usagemay be continually tracked, and average usage reports may be continuallyupdated, such that the pre-payment for each interval is a reflection ofpast actual usage. Each usage report may incorporate usage datamaintained for an indefinite period of time. Alternatively, each usagereport may incorporate usage data maintained for a particular number ofpast intervals (e.g., the past six months, the past twelve months,etc.). Additionally or alternatively, each usage report may permit“resetting” of the data incorporated therein, in accordance with certainevents (e.g., moving, changing job locations, etc.), such that the usagereport may more quickly respond to large changes in actual usage.

In another embodiment, payment may be rendered on a post-paymentschedule directly in accordance with actual usage. Payment may berendered at regular intervals (e.g., every week, every two weeks, everymonth, etc.) in accordance with vehicle user preference and/or asrequired by a particular payee party. VCA computing device 102 mayallocate payment amounts based upon determined and/or tracked actualusage in accordance with vehicle policies 210. In some embodiments,payment management module 224 (and/or vehicle users) may initiatepayments to be made (as described herein) in a typical “receive bill forbill amount, pay bill in bill amount with payment account” fashion, atthese regular intervals.

Additionally or alternatively, payment management module 224 (and/orvehicle users) may initiate payments to be made on a rolling basis(e.g., after every trip, each day, etc.).

In one exemplary embodiment, payment management module 224 receives(e.g., from cost allocation module 222, shown in FIG. 2) an indicationof the respective portions of vehicle costs allocated to (i.e., to bepaid by) each vehicle user. Payment management module 224 may accessfinancial account information associated with each vehicle user.Financial account information may be stored (e.g., in memory 108, shownin FIG. 1) in an encrypted and/or anonymized fashion. Payment managementmodule 224 may then access a financial account for each vehicle user.

In one embodiment, each vehicle user maintains a pre-paid account 402associated specifically with shared vehicle system 100. In someembodiments, this pre-paid account 402 is maintained at the samefinancial institution 114 as one or more other financial accounts 404 ofthe vehicle user (e.g., a savings account or checking account). Thevehicle user may use financial account 404 to pre-fund pre-paid account402 with money (whether or not financial account 404 is maintained atthe same financial institution 114 as pre-paid account 402). The vehicleuser may ensure funds are present in pre-paid account 402, such thatpayments may be made automatically (e.g., without requesting a specificamount be transferred to pre-paid account 402 before the payment can bemade). In some embodiments, payment management module 224 may withdrawpayments from pre-paid account 402 in accordance with the portion ofeach vehicle cost owed by the vehicle user. Pre-paid account 402 mayhave an alert functionality configured to alert the associated vehicleuser when a balance of pre-paid account 402 falls below a particularthreshold amount (e.g., $50 or $20), to avoid a zero or negativebalanced of pre-paid account 402. It should be understood that, in somecases, pre-paid account 402 and financial account 404 may be the sameaccount. In such cases, payments may be made in a typical “automaticbill” fashion, when initiated by payment management module 224 asdescribed herein.

To initiate a payment, payment management module 224 transmits paymentinstructions 410 to the financial institution 114 at which pre-paidaccount 402 (and/or any other financial account 404 from which a vehicleuser makes payments) is maintained. Payment instructions 410 include oneor more payment amounts 412, and cause financial institution 114 toautomatically withdraw funds in the payment amount(s) from pre-paidaccount 402. In some embodiments, payment instructions 410 (as shown inFIG. 4) include a plurality of payment amounts 412, as well as acorresponding plurality of payee parties (e.g., financial accountsdetails thereof) to which the payment amounts 412 are due. In theseembodiments, payment instructions 410 cause financial institution 114 toautomatically initiate transfer of funds each payment amount 412 to thecorresponding financial institution 114 associated with the payee partyto which the payment amount 412 is due.

In another embodiment, to avoid making a plurality of transfers for thepayment of a single bill from a payee party, payment management module224 may include in payment instructions 410 the financial accountinformation of an intermediate account 414. Intermediate account 414 maybe associated with VCA computing device 102 and/or shared vehicle system100. In these embodiments, payment instructions 410 may cause financialinstitution 114 to automatically transfer funds in each payment amount412 to intermediate account 414 (e.g., in separate transfers or as a sumof all individual payment amounts 412). Once funds have been transferredto intermediate account 414 from every pre-paid account 402 associatedwith each vehicle user, such that intermediate account 414 includesfunds in a total bill amount due to a payee party, payment managementmodule 224 initiates a transfer of funds from intermediate account 414to the financial institution 114 of the payee party (e.g., with anotherset of payment instruction 410).

In some cases, funds may be transferred between pre-paid accounts 402 ofvehicle users associated with the same vehicle. For example, if onevehicle user “pre-paid” fuel costs for all vehicle users of a group bypaying for gas at a gas pump (e.g., paying $40.00 from their pre-paidaccount and/or any other account), payment management module 224 may beconfigured to transfer funds associated with the other vehicle users'respective fuel costs to the pre-paid account 402 of that vehicle user.In some embodiments, for situations like these and/or for other paymentssituations (e.g., for maintenance costs, tolls, parking fees, etc.), oneor more of the vehicle users may maintain a joint account (e.g., apre-paid account 402 and/or any other financial account 404) from whichtotal bill amounts may be withdrawn.

Exemplary User Computer Device

FIG. 5 depicts an exemplary configuration of an exemplary user computerdevice 502 that may be used with shared vehicle system 100 (shown inFIG. 1), in accordance with one embodiment of the present disclosure.User computer device 502 may be operated by a user 501 (e.g., a vehicleuser). User computer device 502 may include, but is not limited to, usercomputing devices 110 (shown in FIG. 1). User computer device 502 mayinclude a processor 505 for executing instructions. In some embodiments,executable instructions may be stored in a memory area 510. Processor505 may include one or more processing units (e.g., in a multi-coreconfiguration). Memory area 510 may be any device allowing informationsuch as executable instructions and/or transaction data to be stored andretrieved. Memory area 510 may include one or more computer-readablemedia.

User computer device 502 also may include at least one media outputcomponent 515 for presenting information to user 501. Media outputcomponent 515 may be any component capable of conveying information touser 501. In some embodiments, media output component 515 may include anoutput adapter (not shown), such as a video adapter and/or an audioadapter. An output adapter may be operatively coupled to processor 505and operatively coupleable to an output device, such as a display device(e.g., a cathode ray tube (CRT), liquid crystal display (LCD), lightemitting diode (LED) display, or “electronic ink” display) or an audiooutput device (e.g., a speaker or headphones).

In some embodiments, media output component 515 may be configured topresent a graphical user interface (e.g., a web browser and/or a clientapplication) to user 501. A graphical user interface may include, forexample, an online store interface for viewing and/or purchasing items,and/or a wallet application for managing payment information.

In some embodiments, user computer device 502 may include an inputdevice 520 for receiving input from user 501. User 501 may use inputdevice 520 to, without limitation, interact with vehicle 104 and/or VCAcomputing device 102 (e.g., using an app), input trip information,and/or request payment information. Input device 520 may include, forexample, a keyboard, a pointing device, a mouse, a stylus, and/or atouch sensitive panel (e.g., a touch pad or a touch screen). A singlecomponent such as a touch screen may function as both an output deviceof media output component 515 and input device 520. User computer device502 further includes at least one sensor 530, including, for example, agyroscope, an accelerometer, a position detector, a biometric inputdevice, a telematics data collection device, and/or an audio inputdevice.

User computer device 502 may also include a communication interface 525,communicatively coupled to a remote device such as VCA computing device102 (shown in FIG. 1) and/or vehicle computing device 306 (shown in FIG.3). Communication interface 525 may include, for example, a wired orwireless network adapter and/or a wireless data transceiver for use witha mobile telecommunications network.

Stored in memory area 510 may be, for example, computer-readableinstructions for providing a user interface to user 501 via media outputcomponent 515 and, optionally, receiving and processing input from inputdevice 520. The user interface may include, among other possibilities, aweb browser and/or a client application. Web browsers enable users, suchas user 501, to display and interact with media and other informationtypically embedded on a web page or a website from VCA computing device102 and/or vehicle computing device 306. A client application may allowuser 501 to interact with, for example, VCA computing device 102 and/orvehicle computing device 306. For example, instructions may be stored bya cloud service and the output of the execution of the instructions sentto the media output component 515.

Exemplary Server Device

FIG. 6 depicts an exemplary configuration of an exemplary servercomputer device shown in FIG. 1, in accordance with one embodiment ofthe present disclosure. A server computer device 602 may include, but isnot limited to, database server 106, VCA computing device 102, insuranceserver 112, (all shown in FIG. 1) and/or vehicle computing device 306(shown in FIG. 3). Server computer device 602 may include a processor605 for executing instructions. Instructions may be stored in a memoryarea 610. Processor 605 may include one or more processing units (e.g.,in a multi-core configuration).

Processor 605 may be operatively coupled to a communication interface615 such that server computer device 602 may be capable of communicatingwith a remote device such as another server computer device 602, usercomputer device 502 (shown in FIG. 5), or VCA computing device 102. Forexample, communication interface 615 may receive requests from ortransmit requests to user computer device 502 via the Internet.

Processor 605 may also be operatively coupled to a storage device 620.Storage device 620 may be any computer-operated hardware suitable forstoring and/or retrieving data, such as, but not limited to, dataassociated with database 108 (shown in FIG. 1). In some embodiments,storage device 620 may be integrated in server computer device 602. Forexample, server computer device 602 may include one or more hard diskdrives as storage device 620. In other embodiments, storage device 620may be external to server computer device 602 and may be accessed by aplurality of server computer devices 6. For example, storage device 620may include a storage area network (SAN), a network attached storage(NAS) system, and/or multiple storage units such as hard disks and/orsolid state disks in a redundant array of inexpensive disks (RAID)configuration.

In some embodiments, processor 605 may be operatively coupled to storagedevice 620 via a storage interface 625. Storage interface 625 may be anycomponent capable of providing processor 605 with access to storagedevice 620. Storage interface 625 may include, for example, an AdvancedTechnology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, aSmall Computer System Interface (SCSI) adapter, a RAID controller, a SANadapter, a network adapter, and/or any component providing processor 605with access to storage device 620.

Processor 605 executes computer-executable instructions for implementingaspects of the disclosure. In some embodiments, processor 605 may betransformed into a special purpose microprocessor by executingcomputer-executable instructions or by otherwise being programmed. Forexample, processor 605 may be programmed with the instructions such asare illustrated in FIG. 7.

Exemplary Computer-Implemented Method for Allocating Vehicle CostsBetween Users of a Vehicle

FIG. 7 depicts a flow chart of an exemplary computer-implemented method700 for allocating vehicle costs between users of a vehicle using sharedvehicle system 100 shown in FIG. 1. In the exemplary embodiment, method700 may be performed by VCA computing device 102 (shown in FIG. 1).

Method 700 may include receiving 702 a plurality of trip reportsassociated with a corresponding plurality of trips performed using avehicle within a predetermined interval of time. Each trip of theplurality of trips is associated with one or more vehicle users of aplurality of vehicle users associated with the vehicle. Method 700 mayfurther include generating 704 a total vehicle usage report based atleast in part upon the plurality of trip reports. The total vehicleusage report describes the total usage of the vehicle by the pluralityof vehicle users over the interval of time. Method 700 may also includedetermining 706 a total vehicle cost associated with the vehicle overthe interval of time based at least in part upon the total vehicle usagereport.

Method 700 may still further include generating 708 a respective userusage report associated with each vehicle user of the plurality ofvehicle users, based at least in part upon one or more trip reports ofthe plurality of trip reports associated with the corresponding vehicleuser. Method 700 may also include determining 710 a respective vehicleuser cost (e.g., portion of the total vehicle cost) attributable to eachvehicle user of the plurality of vehicle users based at least in partupon the corresponding user usage report for the corresponding vehicleuser and the total vehicle cost. Method 700 may further includeallocating 712 each respective vehicle user cost to the correspondingvehicle user.

Exemplary Computer Device for Allocating Vehicle Costs Between Users ofa Vehicle

FIG. 8 depicts a diagram 800 of components of one or more exemplarycomputing devices 810 that may be used in shared vehicle system 100shown in FIG. 1. In some embodiments, computing device 810 may besimilar to VCA computing device 102 (shown in FIG. 1). In the exemplaryembodiment, computing device 810 may include a database 820, which maybe similar to database 108 (shown in FIG. 1). Database 820 may includetrip reports 822, total vehicle usage reports 824, user usage reports826, and vehicle policies 828. Database 820 may be coupled with severalseparate components within computing device 810, which perform specifictasks.

In one exemplary embodiment, computing device 810 may include areceiving component 830. In some embodiment, receiving component 830 mayinclude and/or be integral to any kind of communication device (e.g., atransceiver). Receiving component 830 may be configured to receive aplurality of trip reports 822 associated with a corresponding pluralityof trips performed using a vehicle within a predetermined interval oftime. Each trip of the plurality of trips may be associated with one ormore vehicle users of a plurality of vehicle users associated with thevehicle.

Computing device 810 may also include a generating component 840.Generating component 840 may be configured to generate a total vehicleusage report 824 based at least in part upon the plurality of tripreports 822. The total vehicle usage report 824 may describe the totalusage of the vehicle by the plurality of vehicle users over the intervalof time. Generating component 840 may also be configured to generate arespective user usage report 826 associated with each vehicle user ofthe plurality of vehicle users, based at least in part upon one or moretrip reports 822 of the plurality of trip reports 822 associated withthe corresponding vehicle user.

Computing device 810 may further include a determining component 850.Determining component 850 may be configured to determine a total vehiclecost associated with the vehicle over the interval of time based atleast in part upon the total vehicle usage report 824. Determiningcomponent 850 may be further configured to determine a respectivevehicle user cost attributable to each vehicle user of the plurality ofvehicle users based at least in part upon the corresponding user usagereport 826 for the corresponding vehicle user and the total vehiclecost.

Computing device 810 may also include an allocating component 860,configured to allocate each respective vehicle user cost to thecorresponding vehicle user. Allocating may include, for example,recording the respective vehicle user cost and/or transmitting a messageincluding the respective vehicle user cost to the corresponding vehicleuser (e.g., to a user computing device associated with the vehicleuser). Computing device 810 may further include, in some embodiments, apayment management component 870. Payment management component 870 maybe configured to manage payments of the vehicle user cost(s) torespective payee parties (e.g., an insurance company, a car dealership,a repair shop, a financial institution, etc.).

Managing payments may include transmitting the message including therespective vehicle user cost, as well as portions of the respectivevehicle cost payable to each payee party, such that the vehicle user maypay the payee party. Managing payments may additionally or alternativelyinclude transmitting withdrawal and transfer instructions to one or morefinancial institutions associated with the vehicle user to cause paymentof the vehicle user costs from a payment account of each vehicle user.Additionally, a processing component 880 may assist with execution ofcomputer-executable instructions associated with the system.

Additional Exemplary Computer-Implemented Methods for Allocating VehicleCosts Between Users of a Vehicle

FIG. 9 illustrates a flow chart of another exemplarycomputer-implemented method 900 for allocating vehicle costs betweenusers of a vehicle, using the shared vehicle system 100 shown in FIG. 1.In the exemplary embodiment, method 900 may be performed by VCAcomputing device 102 (shown in FIG. 1).

Method 900 may include receiving 902 a potential trip report associatedwith a potential future trip to be performed using a vehicle. Thepotential trip report may be associated with at least one vehicle userincluding an anticipated driver of the vehicle and an anticipatedpassenger, and may include an anticipated destination. Method 900 mayalso include retrieving 904 insurance policy information associated withat least one of the vehicle and the anticipated driver of the vehicle.

Method 900 may also include generating 906 an anticipated insurance costbased upon the anticipated driver of the vehicle and the anticipateddestination, and allocating 908 the anticipated insurance cost betweenthe anticipated driver and the anticipated passenger. Method 900 mayfurther include transmitting 910 the anticipated insurance cost to oneor more computing devices for review by the anticipated driver.

FIG. 10 illustrates a flow chart of yet another exemplarycomputer-implemented method 1000 for allocating vehicle costs betweenusers of a vehicle, using the shared vehicle system 100 shown in FIG. 1.In the exemplary embodiment, method 1000 may be performed by VCAcomputing device 102 (shown in FIG. 1).

Method 1000 may include receiving 1002 a trip report associated with atrip performed using a vehicle. The trip report may be associated with aplurality of vehicle users of the vehicle, and may include anidentification of a distance of the trip. Method 1000 may also includedetermining 1004 which vehicle user of the plurality of vehicle users isa driver of the trip, and retrieving 1006 insurance policy informationassociated with the driver of the trip.

Method 1000 may further include calculating 1008 an insurance costassociated with the trip based at least in part upon the insurancepolicy information and the distance of the trip, and allocating 1010 theinsurance cost between the plurality of vehicle users.

Exemplary Autonomous or Semi-Autonomous Vehicle Functionality

FIG. 11 depicts a view of an exemplary vehicle 1100. In the exemplaryembodiment, vehicle 1100 may be an autonomous or semi-autonomous vehiclecapable of fulfilling the transportation capabilities of a traditionalautomobile or other vehicle. In these embodiments, vehicle 1100 may becapable of sensing its environment and navigating without human input.In other embodiments, vehicle 1100 is a manual vehicle, such as atraditional automobile that is controlled by a driver 1115, and may besimilar to vehicle 104 shown in FIGS. 1 and 3.

Vehicle 1100 may include a plurality of sensors 1105 and a vehiclecontroller 1110 (which may include and/or be similar to vehiclecomputing device 306, shown in FIG. 3). The plurality of sensors 1105may detect the current surroundings and location of vehicle 1100.Plurality of sensors 1105 may include, but are not limited to, radar,LIDAR, Global Positioning System (GPS), video devices, imaging devices,cameras, audio recorders, and computer vision. Plurality of sensors 1105may also include sensors that detect conditions of vehicle 1100, such asspeed, acceleration, gear, braking, and other conditions related to theoperation of vehicle 1100, for example: at least one of a measurement ofat least one of speed, direction, rate of acceleration, rate ofdeceleration, location, position, orientation, and rotation of thevehicle, and a measurement of one or more changes to at least one ofspeed, direction, rate of acceleration, rate of deceleration, location,position, orientation, and rotation of the vehicle. Furthermore,plurality of sensors 1105 may include impact sensors that detect impactsto vehicle 1100, including force and direction, and sensors that detectactions of vehicle 1100, such the deployment of airbags. In someembodiments, plurality of sensors 1105 may detect the presence of driver1115 and one or more passengers 1120 in vehicle 1100. In theseembodiments, plurality of sensors 1105 may detect the presence offastened seatbelts, the weight in each seat in vehicle 1100, heatsignatures, or any other method of detecting information about driver1115 and passengers 1120 in vehicle 1100, including those methods ofdetermining occupants described herein.

In certain embodiments, plurality of sensors 1105 may include occupantposition sensors to determine a location and/or position of eachoccupant (i.e., driver 1115 and passengers 1120) in vehicle 1100. Thelocation of an occupant may identify a particular seat or other locationwithin vehicle 1100 where the occupant is located. The position of theoccupant may include the occupant's body orientation, the location ofspecific limbs, and/or other positional information. In one example,plurality of sensors 1105 may include an in-cabin facing camera, LIDAR,radar, weight sensors, accelerometer, gyroscope, compass and/or othertypes of sensors to identify the location and/or position of occupantswithin vehicle 1100.

Vehicle controller 1110 may interpret the sensory information toidentify appropriate navigation paths, detect threats, and react toconditions. In some embodiments, vehicle controller 1110 may be able tocommunicate with one or more remote computer devices, such as usercomputing device 1125. In the example embodiment, user computing device1125 is associated with driver 1115 and includes one or more internalsensors, such as an accelerometer, a gyroscope, and/or a compass. Usercomputing device 125 may be capable of communicating with vehiclecontroller 1110 wirelessly. In addition, vehicle controller 1110 anduser computing device 1125 may be configured to communicate withcomputer devices located remotely from vehicle 1100.

In some embodiments, vehicle 1100 may include autonomous orsemi-autonomous vehicle-related functionality or technology that may beused with the present embodiments to replace human driver actions mayinclude and/or be related to the following types of functionality: (a)fully autonomous (driverless); (b) limited driver control; (c)vehicle-to-vehicle (V2V) wireless communication; (d)vehicle-to-infrastructure (and/or vice versa) wireless communication;(e) automatic or semi-automatic steering; (f) automatic orsemi-automatic acceleration; (g) automatic or semi-automatic braking;(h) automatic or semi-automatic blind spot monitoring; (i) automatic orsemi-automatic collision warning; (j) adaptive cruise control; (k)automatic or semi-automatic parking/parking assistance; (l) automatic orsemi-automatic collision preparation (windows roll up, seat adjustsupright, brakes pre-charge, etc.); (m) driver acuity/alertnessmonitoring; (n) pedestrian detection; (o) autonomous or semi-autonomousbackup systems; (p) road mapping systems; (q) software security andanti-hacking measures; (r) theft prevention/automatic return; (s)automatic or semi-automatic driving without occupants; and/or otherfunctionality. In these embodiments, the autonomous or semi-autonomousvehicle-related functionality or technology may be controlled, operated,and/or in communication with vehicle controller 1110.

The wireless communication-based autonomous or semi-autonomous vehicletechnology or functionality may include and/or be related to: automaticor semi-automatic steering; automatic or semi-automatic accelerationand/or braking; automatic or semi-automatic blind spot monitoring;automatic or semi-automatic collision warning; adaptive cruise control;and/or automatic or semi-automatic parking assistance. Additionally oralternatively, the autonomous or semi-autonomous technology orfunctionality may include and/or be related to: driver alertness orresponsive monitoring; pedestrian detection; artificial intelligenceand/or back-up systems; navigation or GPS-related systems; securityand/or anti-hacking measures; and/or theft prevention systems.

Moreover, where vehicle 1100 is an autonomous or semi-autonomousvehicle, vehicle controller 1110 may interpret sensory information fromsensors 1105 to determine usage of vehicle 1100 by one or more vehicleusers (e.g., driver 1115 and/or passengers 1120) for each tripundertaken by vehicle 1100. Determining usage of vehicle 1100 by one ormore vehicle users may facilitate monitoring, allocating, and dividingusage-based vehicle costs between the vehicle users. Usage-based vehiclecosts include one or more of asset costs (e.g., in those cases in whicha vehicle policy dictates allocation of asset costs according to usage,as described herein), insurance costs (e.g., in those cases in which avehicle policy dictates allocation of insurance costs according tousage, as described herein), fuel costs (e.g., in those cases in which avehicle policy dictates allocation of fuel costs according to usage, asdescribed herein), maintenance costs (e.g., in those cases in which avehicle policy dictates allocation of maintenance costs according tousage, as described herein), and incidental costs (e.g., in those casesin which a vehicle policy dictates allocation of one or more incidentalcosts according to usage, as described herein).

In addition, vehicle controller 1110 may interpret the sensoryinformation to identify vehicle users (e.g., driver 1115 and/orpassengers 1120) present in vehicle 1100 during a trip. For example,vehicle computer device 1110 may determine positional information for atleast one vehicle user of vehicle 1100 present in vehicle 1100 during atrip. Positional information may include a position of a vehicle user, adirection of facing of the vehicle user, a size of the vehicle user,and/or a skeletal positioning of the vehicle user. The position of thevehicle user may include which seat the vehicle user occupies. Thedirection of facing of the vehicle user may include whether the vehicleuser is facing forward, reaching forward, reaching to the side, and/orhas his/her head turned. The size of the vehicle user may determinewhether the vehicle user is an adult or a child. The size of the vehicleuser may also include the vehicle user's height. The skeletalpositioning may include positioning of the vehicle user's joints, spine,arms, legs, torso, neck face, head, major bones, hands, and/or feet.

Where vehicle 1100 is a semi-autonomous or regular vehicle, such that adriver 1115 controls vehicle 1100 during part or the entirety of one ormore trips, vehicle controller 1110 may interpret sensory information todevelop a driving profile for driver 1115 and/or to determine, basedupon developed driving profiles, which vehicle user is a driver 1115 fora trip.

For example, vehicle controller 1110 may collect vehicle telematics datafrom user computing device 1125 and/or one or more of sensors 1105.Vehicle telematics data may include data from user computing device 1125and/or one or more of sensors 1105 and may include navigation,communications, safety, security, and/or “infotainment” data. Forexample, vehicle telematics data collected and analyzed by vehiclecontroller 1110 may include, but is not limited to braking and/oracceleration data, navigation data, vehicle settings (e.g., seatposition, mirror position, temperature or air control settings, etc.),remote-unlock and/or remote-start data (e.g., determining which usercomputing device 1125 is used to unlock or start vehicle 1100) and/orany other telematics data.

In some embodiments, collecting and monitoring vehicle telematics datamay enable developing a profile or status of vehicle 1100 and/ordriver(s) 1115 thereof, during autonomous, semi-autonomous, and/oruser-driven trips. For example, vehicle controller 1110 may develop avehicle or autonomous profile that characterizes the driving ofvehicle-driven trips by vehicle 1100 based upon vehicle telematics datacollected during known vehicle-driven or autonomous trips. Vehiclecontroller 1110 may additionally develop driver profiles for eachvehicle user that acts as a driver 1115 of vehicle 1100. Vehiclecontroller 1110 may compare collected telematics data to one or moredeveloped driver profiles to determine driver 1115 for a trip.Accordingly, one or more usage-based costs that are calculated and/orallocated based upon an identity of driver 1115 may be calculated and/orallocated properly. Specifically, vehicle controller 1110 may usecollected vehicle telematics data to more accurately determineusage-based insurance cost allocation by more accurately identifyingdrivers 1115 of vehicle 1100 and/or tracking a level of risk of any onedriver 1115 during a trip. For example, a driver 1115 may have aparticularly low insurance rate but may exhibit one or more high-riskbehaviors, according to collected vehicle telematics data (e.g., highoccurrence of abrupt deceleration, particularly fast turns, and/orextreme acceleration). Accordingly, vehicle controller 1110 may usecollected vehicle telematics data to adjust an insurance rate associatedwith driver 1115 and/or allocate a higher percentage of an insurancecost to driver 1115. Moreover, in an event of an accident or vehicularcrash, vehicle controller 1110 may facilitate determining driver 1115 toassist in determining allocation of incidental costs associated with theaccident. Additionally or alternatively, vehicle controller 1110 may usecollected vehicle telematics data to determine a status of vehicle 1100before and after the accident to assist in determining repair costsand/or generating an insurance claim.

In one aspect of the present disclosure, a vehicle cost allocation (VCA)computing device (e.g., vehicle controller 1110) for allocating vehiclecosts between users of a vehicle may be provided. The VCA computingdevice may include a memory and a processor, wherein the processor isprogrammed to receive vehicle telematics data from one or more sensorswithin the vehicle, and, based upon the received vehicle telematicsdata, identify one or more vehicle users present in the vehicle during atrip. The processor may be further programmed to determine a vehiclecost associated with the trip, and allocate a respective portion of thevehicle cost to each of the one or more vehicle users.

In another aspect, a computer-implemented method for allocating vehiclecosts between users of a vehicle may be provided. The method may beimplemented using a vehicle cost allocation (VCA) computing device(e.g., vehicle controller 1110) including a processor and a memory. Themethod may include receiving vehicle telematics data from one or moresensors within the vehicle, and based upon the received vehicletelematics data, identifying one or more vehicle users present in thevehicle during a trip. The method may also include determining a vehiclecost associated with the trip, and allocating a respective portion ofthe vehicle cost to each of the one or more vehicle users.

While vehicle 1100 may be an automobile in the exemplary embodiment, inother embodiments, vehicle 1100 may be, but is not limited to, othertypes of ground craft, aircraft, and watercraft vehicles.

Exemplary Insurance-Related Functionality

In another aspect, a computer-implemented method of allocating vehiclecosts between users of a vehicle, the vehicle costs including aninsurance cost, may be provided. The method may include (i) receiving atrip report associated with a trip performed using a vehicle, the tripassociated with one or more vehicle users of a plurality of vehicleusers of the vehicle; (ii) determining which vehicle user of the one ormore vehicle users is a driver for the trip; (iii) retrieving insurancepolicy information associated with the driver; (iv) retrieving one ormore vehicle policies provided by the plurality of vehicle users; (v)determining an insurance cost associated with the trip based at least inpart upon the insurance policy information and the one or more vehiclepolicies; and/or (vi) allocating the insurance cost between the one ormore vehicle users. The method may include additional, less, oralternate functionality, including that discussed elsewhere herein.

Additionally or alternatively, the method may include determining one ormore other vehicle costs associated with the trip, such as fuel costsand/or maintenance costs. The method may also include allocating the oneor more other vehicle costs based at least in part upon the one or morevehicle policies. Additionally or alternatively, the method may includeallocating a first portion of the one or more vehicle costs to thedriver, and/or allocating a second portion, the second portion greaterthat the first portion, of the one or more other vehicle costs to eachother vehicle user of the one or more vehicle users. For instance, ifthe driver for the trip has a lower associated insurance rate andtherefore is chosen and/or requested to drive for the trip, the drivermay be allocated a lower portion of, for example, fuel costs than theirpassengers, to compensate for the lower insurance rate incurred and/orthe effort of driving. Additionally or alternatively, the method mayinclude allocating equal portions of the insurance costs between allvehicle users associated with the trip, wherein the insurance cost forthe trip is determined based upon which vehicle user is the driver forthe trip.

In a further aspect, a computer-implemented method of allocating vehiclecosts between users of a vehicle may be provided. The method may include(i) receiving a potential trip report associated with a potential futuretrip to be performed using a vehicle, the potential trip reportassociated with at least one vehicle user including an anticipateddriver of the vehicle and an anticipated passenger, the potential tripreport including an anticipated destination; (ii) retrieving insurancepolicy information associated with at least one of the vehicle and theanticipated driver of the vehicle; (iii) generating an anticipatedinsurance cost based upon the anticipated driver of the vehicle and theanticipated destination; (iv) allocating the anticipated insurance costbetween the anticipated driver and the anticipated passenger; and/ortransmitting the anticipated insurance cost to one or more computingdevices for review by the anticipated driver.

Additionally or alternatively, the method may include determining acurrent location of the vehicle using at least one GPS sensor,determining an anticipated route associated with the potential tripbased upon the current location of the vehicle and the anticipateddestination, and/or calculating at least one of an anticipated number ofmiles driven and anticipated amount of time driven for the anticipatedroute, to generate the anticipated insurance cost based upon the atleast one of an anticipated number of miles driven and anticipatedamount of time driven. The method may include retrieving a current fuelcost associated with at least one of the current location of the vehicleand the anticipated route, calculating an anticipated fuel costassociated with the trip based upon the current fuel cost and theanticipated number of miles driven, and/or transmitting the anticipatedfuel cost to one or more computing devices for review by the anticipateddriver. The method may also include identifying one or more incidentalcosts associated with the anticipated trip, and/or transmitting the oneor more anticipated incidental costs to one or more computing devicesfor review by the anticipated driver. The method may further include, insome embodiments, receiving an affirmative response indicating thepotential trip is to be taken, and/or transmitting a hold instruction toa respective financial account of the anticipated driver and theanticipated passenger to hold funds in an amount of the allocatedinsurance cost.

In yet another aspect, a computer-implemented method of allocatingvehicle costs between users of a vehicle may be provided. The method mayinclude (i) receiving a trip report associated with a trip performedusing a vehicle, the trip report associated with a plurality of vehicleusers of the vehicle and including an identification of a distance ofthe trip; (ii) determining which vehicle user of the plurality ofvehicle users is a driver of the trip; (iii) retrieving insurance policyinformation associated with the driver of the trip; (iv) calculating aninsurance cost associated with the trip based at least in part upon theinsurance policy information and the distance of the trip; and/or (v)allocating the insurance cost between the plurality of vehicle users.

Additionally or alternatively, the method may include identifying amileage rate in the insurance policy information, the mileage ratedescribing an insurance rate incurred for each mile driven. In otherembodiments, the method may include identifying a mileage rate in theinsurance policy information, the mileage rate describing a firstinsurance rate incurred for each mile driven below a threshold mileagevalue and a second insurance rate incurred for each mile drive above thethreshold mileage value, the second insurance rate higher than the firstinsurance rate.

Exemplary Embodiments and Methods

The present embodiments may additionally provide automated paymentmanagement of the respective user portions of the total vehicle cost. Inthese embodiments, VCA computing device 102 may not only determine whateach vehicle user is obligated to pay but may manage withdrawal and/ortransfer of the appropriate funds to each payee party. Such paymentmanagement may save the vehicle users time and effort and may ensuremore accurate and timely payment to each payee party.

In one aspect, a computer-implemented method managing payment of vehiclecosts for users of a shared vehicle is provided. The method may include(1) determining a respective portion of a total vehicle cost to beallocated to each vehicle user of a plurality of vehicle usersassociated with a vehicle, the total vehicle cost associated the vehicleover a predetermined interval of time; (2) accessing a respectivepre-paid account associated with each vehicle user; and/or (3)transmitting instructions to a respective financial institutionassociated with each pre-paid account to withdraw funds corresponding tothe respective portion of the total vehicle cost. The method may includeadditional, less, or alternate functionality, including that discussedelsewhere herein.

For instance, the method may include dividing each respective portion ofthe total vehicle cost into a plurality of payments, each payment of theplurality of payments associated with a different payee. The method mayfurther include transmitting instructions to the respective financialinstitution associated with each pre-paid account to transfer fundscorresponding to each respective payment of the plurality of payments toa payment account of the corresponding payee.

Additionally or alternatively, the method may include identifying afirst segment of the total vehicle cost, the first segment independentof the respective portions and equally associated with the plurality ofvehicle users. For example, the first segment may represent amaintenance cost that is divided equally among the vehicle usersregardless of usage. The method may further include accessing a jointpre-paid account associated with the plurality of vehicle users. Themethod may also include transmitting instructions to a financialinstitution associated with the joint pre-paid account to withdraw fundscorresponding to the first segment of the total vehicle cost.

Additional Embodiments

In one aspect, a computer-implemented method for allocating vehiclecosts between users of a vehicle may be provided. The vehicle costs mayinclude an insurance cost. The method may be implemented using a vehiclecost allocation (VCA) computing device including a processor and amemory. The method may include (1) receiving, via one or more processorsand/or transceivers, a trip report and/or sensor data associated with atrip performed using a vehicle (either pre-trip or post-trip), the tripassociated with one or more vehicle users of multiple vehicle users ofthe vehicle (such as via wireless communication or data transmissionover one or more radio links or wireless communication channels, thetrip report and sensor data being transmitted by a vehicle controller ora user mobile device); (2) determining, via the one or more processors,which vehicle user of the one or more vehicle users is a driver for thetrip based upon the sensor data received; (3) retrieving, via the one ormore processors, insurance policy information and/or a risk profileassociated with the driver from a memory unit; (4) determining, via theone or more processors, a usage-based insurance cost (such as mileage ortime based insurance premium or cost, or a pay-by-mile insurancepremium) associated with the trip based at least in part upon (i) theinsurance policy information and/or risk profile associated with thedriver, and/or (ii) the trip report; and/or (5) transmitting, via theone or more processors and/or transceivers, the usage-based insurancecost to the driver's mobile device or vehicle controller via wirelesscommunication or data transmission over one or more radio links orwireless communication channels for the driver's review and/or approval(either before or after the trip) to facilitate allocating the insurancecost between the one or more vehicle users.

In another aspect, a computer-implemented method for allocating vehiclecosts between users of a vehicle may be provided. The method may beimplemented using a vehicle cost allocation (VCA) computing deviceincluding a processor and a memory. The method may include (1)receiving, via one or more processors and/or transceivers (such as viawireless communication or data transmission over one or more radio linksor wireless communication channels), (i) vehicle data identifying avehicle, (ii) a proposed trip report, and/or (iii) sensor dataassociated with a driver of the vehicle (from a driver mobile device ora vehicle-mounted controller/computer) before a trip is taken using avehicle, the vehicle having multiple vehicle users of the vehicle (thetrip report and sensor data being transmitted by a vehicle controller ora user mobile device); (2) determining, via the one or more processors,an identity of the driver from among the multiple users of the vehiclefor the trip based upon the sensor data received; (3) retrieving, viathe one or more processors, insurance policy information and/or a riskprofile associated with the driver identified from a memory unit; (4)determining, via the one or more processors, a usage-based insurancecost associated with the trip based at least in part upon the insurancepolicy information and/or risk profile associated with the driveridentified, and/or a usage-based insurance cost adjustment based uponthe proposed trip report; and/or (5) transmitting, via the one or moreprocessors and/or transceivers, the usage-based insurance cost and/orcost adjustment associated with the proposed trip to the driver's mobiledevice or vehicle controller via wireless communication or datatransmission over one or more radio links or wireless communicationchannels for the driver's review and/or approval prior to the trip tofacilitate allocating the insurance cost between the one or more vehicleusers.

In another aspect, a computer-implemented method for allocating vehiclecosts between users of a vehicle may be provided. The method may beimplemented using a vehicle cost allocation (VCA) computing deviceincluding a processor and a memory. The method may include (1)receiving, via one or more processors and/or transceivers (such as viawireless communication or data transmission over one or more radio linksor wireless communication channels), (i) vehicle data identifying avehicle, (ii) a trip report, and/or (ii) sensor data associated with adriver of the vehicle (from a driver mobile device or a vehicle-mountedcontroller/computer) after a trip is taken using a vehicle, the vehiclehaving multiple vehicle users of the vehicle (the vehicle data, the tripreport, and sensor data being transmitted by a vehicle controller or auser mobile device); (2) determining, via the one or more processors, anidentity of the driver from among the multiple users of the vehicle forthe trip based upon the sensor data or trip report received; (3)retrieving, via the one or more processors, insurance policy informationand/or a risk profile associated with the driver identified from amemory unit; (4) determining, via the one or more processors, ausage-based insurance cost associated with the trip based at least inpart upon the insurance policy information and/or risk profileassociated with the driver identified or a usage-based insurance costadjustment for the driver based upon the trip report; and/or (5)transmitting, via the one or more processors and/or transceivers, theusage-based insurance cost or cost adjustment for the trip to thedriver's mobile device or vehicle controller via wireless communicationor data transmission over one or more radio links or wirelesscommunication channels for the driver's review and/or approval after thetrip to facilitate allocating the insurance cost between the one or morevehicle users.

The foregoing methods may include additional, less, or alternatefunctionality, including that discussed elsewhere herein. The foregoingmethods may be implemented via one or more local or remote processors,sensors, transceivers, and/or servers, and/or via computer-executableinstructions stored on non-transitory computer-readable media or medium.

In another aspect, a computer system configured to allocate vehiclecosts between users of a vehicle may be provided. The computer systemcomprising one or more local or remote processors, servers,transceivers, and/or sensors configured to: (1) receive a trip reportand sensor data associated with a trip performed using a vehicle (eitherpre-trip or post-trip), the trip associated with one or more vehicleusers of multiple vehicle users of the vehicle (such as via wirelesscommunication or data transmission over one or more radio links orwireless communication channels, the trip report and sensor data beingtransmitted by a vehicle controller or a user mobile device); (2)determine which vehicle user of the one or more vehicle users is adriver for the trip based upon the sensor data or trip report received;(3) retrieve insurance policy information and/or a risk profileassociated with the driver from a memory unit; (4) determine ausage-based insurance cost associated with the trip based at least inpart upon (i) the insurance policy information and/or risk profileassociated with the driver, and/or (ii) the trip report; and/or (5)transmit the usage-based insurance cost to the driver's mobile device orvehicle controller via wireless communication or data transmission overone or more radio links or wireless communication channels for thedriver's review and/or approval (either before or after the trip) tofacilitate allocating the insurance cost between the one or more vehicleusers.

In another aspect, a computer system configured to allocate vehiclecosts between users of a vehicle may be provided. The computer systemcomprising one or more local or remote processors, transceivers,sensors, and/or servers configured to: (1) receive, via wirelesscommunication or data transmission over one or more radio links orwireless communication channels, (i) vehicle data identifying a vehicle,(ii) a proposed trip report, and/or (iii) sensor data associated with adriver of the vehicle (from a driver mobile device or a vehicle-mountedcontroller/computer) before a trip is taken using a vehicle, the vehiclehaving multiple vehicle users of the vehicle (the vehicle data, the tripreport, and sensor data being transmitted by a vehicle controller or auser mobile device); (2) determine an identify of the driver from amongthe multiple users of the vehicle for the trip based upon the sensordata and/or proposed trip report received; (3) retrieve insurance policyinformation and/or a risk profile associated with the driver identifiedfrom a memory unit; (4) determine a usage-based insurance costassociated with the trip based at least in part upon (i) the insurancepolicy information and/or risk profile associated with the driveridentified, and/or (ii) proposed trip report, and/or determine ausage-based insurance cost adjustment based upon the proposed tripreport; and/or (5) transmit the usage-based insurance cost and/or costadjustment associated with the proposed trip to the driver's mobiledevice or vehicle controller via wireless communication or datatransmission over one or more radio links or wireless communicationchannels for the driver's review and/or approval prior to the trip tofacilitate allocating the insurance cost between the one or more vehicleusers.

In another aspect, a computer system configured to allocate vehiclecosts between users of a vehicle may be provided. The computer systemcomprising one or more local or remote processors, transceivers,sensors, and/or sensors configured to: (1) receive, via wirelesscommunication or data transmission over one or more radio links orwireless communication channels, (i) vehicle data identifying a vehicle,(ii) a trip report, and/or (iii) sensor data associated with a driver ofthe vehicle (from a driver mobile device or a vehicle-mountedcontroller/computer) after a trip is taken using a vehicle, the vehiclehaving multiple vehicle users of the vehicle (the vehicle data, the tripreport, and sensor data being transmitted by a vehicle controller or auser mobile device); (2) determine an identify of the driver from amongthe multiple users of the vehicle for the trip based upon the sensordata and/or trip report received; (3) retrieve insurance policyinformation and/or a risk profile associated with the driver identifiedand/or vehicle from a memory unit; (4) determine a usage-based insurancecost associated with the trip based at least in part upon (i) theinsurance policy information and/or risk profile associated with thedriver identified, and/or (ii) trip report, and/or determine ausage-based insurance cost adjustment for the driver based upon the tripreport and/or risk profile for the driver; and/or (5) transmit theusage-based insurance cost or cost adjustment for the trip to thedriver's mobile device or vehicle controller via wireless communicationor data transmission over one or more radio links or wirelesscommunication channels for the driver's review and/or approval after thetrip to facilitate allocating the insurance cost between the one or morevehicle users and/or readjusting insurance costs post-trip.

The foregoing computer systems may include additional, less, oralternate functionality, including that discussed elsewhere herein.

Additional Considerations

As will be appreciated based upon the foregoing specification, theabove-described embodiments of the disclosure may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware or any combination or subset thereof. Anysuch resulting program, having computer-readable code means, may beembodied or provided within one or more computer-readable media, therebymaking a computer program product, i.e., an article of manufacture,according to the discussed embodiments of the disclosure. Thecomputer-readable media may be, for example, but is not limited to, afixed (hard) drive, diskette, optical disk, magnetic tape, semiconductormemory such as read-only memory (ROM), and/or any transmitting/receivingmedium such as the Internet or other communication network or link. Thearticle of manufacture containing the computer code may be made and/orused by executing the code directly from one medium, by copying the codefrom one medium to another medium, or by transmitting the code over anetwork.

These computer programs (also known as programs, software, softwareapplications, “apps”, or code) include machine instructions for aprogrammable processor, and can be implemented in a high-levelprocedural and/or object-oriented programming language, and/or inassembly/machine language. As used herein, the terms “machine-readablemedium” “computer-readable medium” refers to any computer programproduct, apparatus and/or device (e.g., magnetic discs, optical disks,memory, Programmable Logic Devices (PLDs)) used to provide machineinstructions and/or data to a programmable processor, including amachine-readable medium that receives machine instructions as amachine-readable signal. The “machine-readable medium” and“computer-readable medium,” however, do not include transitory signals.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

As used herein, a processor may include any programmable systemincluding systems using micro-controllers, reduced instruction setcircuits (RISC), application specific integrated circuits (ASICs), logiccircuits, and any other circuit or processor capable of executing thefunctions described herein. The above examples are example only, and arethus not intended to limit in any way the definition and/or meaning ofthe term “processor.”

As used herein, the terms “software” and “firmware” are interchangeable,and include any computer program stored in memory for execution by aprocessor, including RAM memory, ROM memory, EPROM memory, EEPROMmemory, and non-volatile RAM (NVRAM) memory. The above memory types areexample only, and are thus not limiting as to the types of memory usablefor storage of a computer program.

In one embodiment, a computer program is provided, and the program isembodied on a computer readable medium. In an exemplary embodiment, thesystem is executed on a single computer system, without requiring aconnection to a sever computer. In a further embodiment, the system isbeing run in a Windows® environment (Windows is a registered trademarkof Microsoft Corporation, Redmond, Wash.). In yet another embodiment,the system is run on a mainframe environment and a UNIX® serverenvironment (UNIX is a registered trademark of X/Open Company Limitedlocated in Reading, Berkshire, United Kingdom). The application isflexible and designed to run in various different environments withoutcompromising any major functionality. In some embodiments, the systemincludes multiple components distributed among a plurality of computingdevices. One or more components may be in the form ofcomputer-executable instructions embodied in a computer-readable medium.The systems and processes are not limited to the specific embodimentsdescribed herein. In addition, components of each system and eachprocess can be practiced independent and separate from other componentsand processes described herein. Each component and process can also beused in combination with other assembly packages and processes.

As used herein, an element or step recited in the singular and proceededwith the word “a” or “an” should be understood as not excluding pluralelements or steps, unless such exclusion is explicitly recited.Furthermore, references to “exemplary embodiment” or “one embodiment” ofthe present disclosure are not intended to be interpreted as excludingthe existence of additional embodiments that also incorporate therecited features.

The patent claims at the end of this document are not intended to beconstrued under 35 U.S.C. § 112(f) unless traditionalmeans-plus-function language is expressly recited, such as “means for”or “step for” language being expressly recited in the claim(s).

This written description uses examples to disclose the disclosure,including the best mode, and also to enable any person skilled in theart to practice the disclosure, including making and using any devicesor systems and performing any incorporated methods. The patentable scopeof the disclosure is defined by the claims, and may include otherexamples that occur to those skilled in the art. Such other examples areintended to be within the scope of the claims if they have structuralelements that do not differ from the literal language of the claims, orif they include equivalent structural elements with insubstantialdifferences from the literal languages of the claims.

We claim:
 1. A vehicle cost allocation (VCA) computing device for allocating vehicle costs between users of a vehicle, the VCA computing device comprising a memory and a processor, wherein the processor is programmed to: receive, from one or more computing devices associated with at least one vehicle user of the vehicle, an anticipated trip report associated with a future trip to be performed using the vehicle, the anticipated trip report associated with the at least one vehicle user, the at least one vehicle user being one of a driver of the vehicle and a passenger of the vehicle, the anticipated trip report including an anticipated destination and an identification of a first user-specific key capable of accessing the vehicle, the first user-specific key associated with a first vehicle user of the at least one vehicle user; parse the anticipated trip report to identify the first user-specific key; receive, from one or more sensors associated with the vehicle, the first user-specific key and a second user-specific key associated with a second vehicle user of the at least one vehicle user, the first user-specific key and the second user-specific key indicating that the first vehicle user and the second vehicle user have initiated the future trip, the first user-specific key and the second user-specific key provided and registered, during a registration process with the VCA computing device, to the first vehicle user and the second vehicle user respectively, the first user-specific key and second user-specific key each being one of a key fob and an electronic key included in a computing device; identify the first vehicle user as the driver of the future trip by determining that the first user-specific key is associated with the driver of the vehicle; receive, from the one or more sensors, global position system (GPS) coordinates of a current location of the vehicle; in response to receiving the anticipated destination and the GPS coordinates, determine a distance of the future trip based upon the anticipated destination and the GPS coordinates; retrieve, from the memory, a first usage report associated with the first vehicle user and a second usage report associated with the second vehicle user, each usage report generated using information previously collected by the one or more sensors during one or more previous trips performed by each of the first vehicle user and the second vehicle user using the vehicle, each usage report indicating at least one of a cumulative amount, a frequency, and a type of usage of the vehicle i) by each of the first vehicle user and the second vehicle user and ii) associated with the one or more previous trips, wherein a previous driver of the one or more previous trips is one of the first vehicle user and the second vehicle user, and wherein a previous passenger of the one or more previous trips is one of the first vehicle user and the second vehicle user; retrieve, from the memory, insurance policy information associated with the vehicle, the first vehicle user, and the second vehicle user, wherein the insurance policy information includes at least one pre-defined vehicle policy identifying how the vehicle cost is to be allocated between the first vehicle user and the second vehicle user, wherein the at least one pre-defined vehicle policy was agreed to by the first vehicle user and the second vehicle user and stored in the memory during the registration process; generate an anticipated insurance cost based upon the first usage report, the second usage report, the first vehicle user being the driver of the future trip, the at least one pre-defined vehicle policy, the anticipated destination, and the distance of the future trip; allocate the anticipated insurance cost between the first vehicle user and the second vehicle user; and transmit the anticipated insurance cost to the one or more computing devices for review by the driver.
 2. The VCA computing device of claim 1, wherein the processor is further programmed to: determine a current location of the vehicle using at least one GPS sensor associated with the one or more computing devices; determine an anticipated route associated with the future trip based upon at least one of the current location of the vehicle, the anticipated destination, and the distance of the future trip; in response to determining the anticipated route, calculate at least one of an anticipated number of miles driven and an anticipated amount of time driven for the anticipated route; and generate the anticipated insurance cost based upon at least one of the anticipated number of miles driven and the anticipated amount of time driven.
 3. The VCA computing device of claim 2, wherein the processor is further programmed to: retrieve a current fuel cost associated with at least one of the current location of the vehicle and the anticipated route; calculate an anticipated fuel cost associated with the future trip based upon the current fuel cost and the anticipated number of miles driven; and transmit the anticipated fuel cost to the one or more computing devices for review by the driver.
 4. The VCA computing device of claim 2, wherein the processor is further programmed to: identify one or more incidental costs associated with the future trip; and transmit the one or more incidental costs to the one or more computing devices for review by the driver.
 5. The VCA computing device of claim 1, wherein the processor is further configured to: receive the anticipated trip report from a vehicle computing device of the one or more computing devices associated with the at least one vehicle user, the vehicle computing device integral to the vehicle; and transmit the anticipated insurance cost to the vehicle computing device.
 6. The VCA computing device of claim 1, wherein the processor is further configured to: receive the anticipated trip report from a user computing device of the one or more computing devices associated with the at least one vehicle user, the user computing device associated with the driver; and transmit the anticipated insurance cost to the user computing device.
 7. The VCA computing device of claim 1, wherein the processor is further configured to: receive an affirmative response indicating the future trip is to be taken; and transmit a hold instruction to a respective financial account of the first vehicle user and the second vehicle user to hold funds in an amount of each allocated anticipated insurance cost.
 8. The VCA computing device of claim 1, wherein the processor is further configured to: generate, receive, or retrieve vehicle telematics data associated with the vehicle.
 9. The VCA computing device of claim 8, wherein the processor is further configured to: generate the anticipated insurance cost based upon, at least in part, the vehicle telematics data.
 10. The VCA computing device of claim 1, wherein the processor is further programmed to: determine that the first user-specific key is associated with the driver of the vehicle by identifying that the first user-specific key is at least one of paired with the vehicle and used to start the vehicle.
 11. A computer-implemented method for allocating vehicle cost between users of a vehicle, the method implemented using a vehicle cost allocation (VCA) computing device including a processor in communication with a memory, the method comprising, via one or more processors, sensors, servers, or transceivers: receiving, from one or more computing devices associated with at least one vehicle user of the vehicle, an anticipated trip report associated with a future trip to be performed using the vehicle, the anticipated trip report associated with the at least one vehicle user, the at least one vehicle user being one of a driver of the vehicle and a passenger of the vehicle, the anticipated trip report including an anticipated destination and an identification of a first user-specific key capable of accessing the vehicle, the first user-specific key associated with a first vehicle user of the at least one vehicle user; parsing the anticipated trip report to identify the first user-specific key; receiving, from one or more sensors associated with the vehicle, the first user-specific key and a second user-specific key associated with a second vehicle user of the at least one vehicle user, the first user-specific key and the second user-specific key indicating that the first vehicle user and the second vehicle user have initiated the future trip, the first user-specific key and the second user-specific key provided and registered, during a registration process with the VCA computing device, to the first vehicle user and the second vehicle user respectively, the first user-specific key and second user-specific key each being one of a key fob and an electronic key included in a computing device; identifying the first vehicle user as the driver of the future trip by determining that the first user-specific key is associated with the driver of the vehicle; receiving, from the one or more sensors, global position system (GPS) coordinates of a current location of the vehicle; in response to receiving the anticipated destination and the GPS coordinates, determining a distance of the future trip based upon the anticipated destination and the GPS coordinates; retrieving, from the memory, first usage report associated with the first vehicle user and a second usage report associated with the second vehicle user, each usage report generated using information previously collected by the one or more sensors during one or more previous trips performed by each of the first vehicle user and the second vehicle user using the vehicle, each usage report indicating at least one of a cumulative amount, a frequency, and a type of usage of the vehicle i) by each of the first vehicle user and the second vehicle user and ii) associated with the one or more previous trips, wherein a previous driver of the one or more previous trips is one of the first vehicle user and the second vehicle user, and wherein a previous passenger of the one or more previous trips is one of the first vehicle user and the second vehicle user; retrieving, from the memory, insurance policy information associated with the vehicle, the first vehicle user, and the second vehicle user, wherein the insurance policy information includes at least one pre-defined vehicle policy identifying how the vehicle cost is to be allocated between the first vehicle user and the second vehicle user, wherein the at least one pre-defined vehicle policy was agreed to by the first vehicle user and the second vehicle user and stored in the memory during the registration process; generating an anticipated insurance cost based upon the first usage report, the second usage report, the first vehicle user being the driver of the future trip, the at least one pre-defined vehicle policy, the anticipated destination, and the distance of the future trip; allocating the anticipated insurance cost between the first vehicle user and the second vehicle user; and transmitting the anticipated insurance cost to the one or more computing devices for review by the driver.
 12. The computer-implemented method of claim 11 further comprising: determining a current location of the vehicle using at least one GPS sensor associated with the one or more computing devices; determining an anticipated route associated with the future trip based upon at least one of the current location of the vehicle, the anticipated destination, and the distance of the future trip; in response to determining the anticipated route, calculating at least one of an anticipated number of miles driven and an anticipated amount of time driven for the anticipated route; and generating the anticipated insurance cost based upon at least one of the anticipated number of miles driven and the anticipated amount of time driven.
 13. The computer-implemented method of claim 12 further comprising: retrieving a current fuel cost associated with at least one of the current location of the vehicle and the anticipated route; calculating an anticipated fuel cost associated with the future trip based upon the current fuel cost and the anticipated number of miles driven; and transmitting the anticipated fuel cost to the one or more computing devices for review by the driver.
 14. The computer-implemented method of claim 12 further comprising: identifying one or more incidental costs associated with the future trip; and transmitting the one or more incidental costs to the one or more computing devices for review by the driver.
 15. The computer-implemented method of claim 11, wherein receiving the anticipated trip report comprises receiving the anticipated trip report from a vehicle computing device of the one or more computing devices associated with the at least one vehicle user, the vehicle computing device integral to the vehicle, and wherein transmitting the anticipated insurance cost further comprises transmitting the anticipated insurance cost to the vehicle computing device.
 16. The computer-implemented method of claim 11, wherein receiving the anticipated trip report further comprises receiving the anticipated trip report from a user computing device of the one or more computing devices associated with the at least one vehicle user, the user computing device associated with the driver, and wherein transmitting the anticipated insurance cost further comprises transmitting the anticipated insurance cost to the user computing device.
 17. The computer-implemented method of claim 11 further comprising: receiving an affirmative response indicating the future trip is to be taken; and transmitting a hold instruction to a respective financial account of the first vehicle user and the second vehicle user to hold funds in an amount of each allocated anticipated insurance cost.
 18. A vehicle cost allocation (VCA) computing device for allocating vehicle costs between users of a vehicle, the VCA computing device comprising a memory and a processor, wherein the processor is programmed to: receive, from one or more computing devices associated with a plurality of vehicle users of the vehicle, a trip report associated with a trip performed using the vehicle, the trip report associated with the plurality of vehicle users and including an anticipated destination and an identification of a first user-specific key capable of accessing the vehicle, the first user-specific key associated with a first vehicle user of the plurality of vehicle users; parse the trip report to identify the first user-specific key; receive, from one or more sensors associated with the vehicle, a plurality of user-specific keys associated with the plurality of vehicle users, the plurality of user-specific keys including the first user-specific key, the plurality of user-specific keys indicating that at least two vehicle users of the plurality of vehicle users are performing the trip, the plurality of user-specific keys provided and registered, during a registration process with the VCA computing device, to each of the plurality of vehicle users, each of the plurality of user-specific keys being one of a key fob and an electronic key included in a computing device; identify the first vehicle user as a driver of the trip by determining that the first user-specific key is associated with the driver of the vehicle; receive, from the one or more sensors, global position system (GPS) coordinates of a current location of the vehicle; in response to receiving the anticipated destination and the GPS coordinates, determine a distance of the trip based upon the anticipated destination and the GPS coordinates; retrieve, from the memory, a usage report associated with the first vehicle user, the usage report generated using information previously collected by the one or more sensors during one or more previous trips performed by the first vehicle user using the vehicle, the usage report indicating at least one of a cumulative amount, a frequency, and a type of usage of the vehicle by i) the first vehicle user and ii) associated with the one or more previous trips, wherein the first vehicle user is one of a previous driver and a previous passenger in each of the one or more previous trips; retrieve, from the memory, insurance policy information associated with the first vehicle user, wherein the insurance policy information includes at least one pre-defined vehicle policy identifying how the vehicle cost is to be allocated between the plurality of vehicle users, wherein the at least one pre-defined vehicle policy was agreed to by the plurality of vehicle users and stored in the memory during the registration process; calculate an insurance cost associated with the trip based at least in part upon the usage report, the at least one pre-defined vehicle policy, and the distance of the trip; and allocate the insurance cost between the plurality of vehicle users.
 19. The VCA computing device of claim 18, wherein the processor is further programmed to: receive the trip report from a user computing device of the one or more computing devices, the user computing device associated with the driver; and transmit an indication of the insurance cost to the user computing device for review by the driver.
 20. The VCA computing device of claim 18, wherein the processor is further programmed to: receive the trip report from a vehicle computing device of the one or more computing devices, the vehicle computing device integral to the vehicle; and transmit an indication of the insurance cost to the vehicle computing device for review by at least one of the plurality of vehicle users.
 21. The VCA computing device of claim 18, wherein the processor is further programmed to identify a mileage rate in the insurance policy information, the mileage rate describing an insurance rate incurred for each mile driven.
 22. The VCA computing device of claim 18, wherein the processor is further programmed to identify a mileage rate in the insurance policy information, the mileage rate describing a first insurance rate incurred for each mile driven below a threshold mileage value and a second insurance rate incurred for each mile driven above the threshold mileage value, the second insurance rate higher than the first insurance rate. 